Technical data

Supported Software, Technologies, and Protocols
1-4 Oracle iPlanet Web Proxy Server Release Notes
1.4.5 Supported Browsers
Complete information about supported web browsers for Oracle iPlanet Web Proxy
Server 4.0.25 is available in Oracle iPlanet Web Proxy Server 4.0.14+ Certification Matrix,
which is available at:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certific
ation-100350.html
1.4.6 Deprecation Notices
Operating System Versions. As of the release of Oracle iPlanet Web Proxy
Server 4.0.16, the following operating system versions are deprecated and will become
unsupported in a future release of Oracle iPlanet Web Proxy Server:
HP-UX 11.11
Microsoft Windows 2000 Server and Windows 2000 Advanced Server
Red Hat Enterprise Linux Advanced Server 3
Solaris 8
Solaris 9 for SPARC and x86
Web Browser Versions. As of the release of Oracle iPlanet Web Proxy Server 4.0.16, the
following web browser versions are deprecated and will become unsupported in a
future release of Oracle iPlanet Web Proxy Server:
Microsoft Internet Explorer 6
Mozilla 1.4.1 and 1.7.2
Netscape Navigator 7.1 and 7.2
1.5 Supported Software, Technologies, and Protocols
The recent releases of Oracle iPlanet Web Proxy Server include the enhancements
described in the following subsections.
1.5.1 Transparent Proxy
Oracle iPlanet Web Proxy Server 4.0 supports transparent proxy for HTTP/1.1
connections. Transparent proxying involves intercepting and processing web requests
by using the proxy server, without the knowledge or control of clients. For example, a
router for a local network is configured to redirect incoming TCP connections to the
local port, in which the proxy server is active.
Add the following directive to the proxy server
default object in the obj.conf file:
NameTrans fn="host-map"
This configuration enables the proxy server to use the HTTP Host: header of incoming
requests to identify and redirect the request to the target remote server.
Note: Transparent proxy servers that decide connections based on
the HTTP
Host: headers are vulnerable to fake HTTP Host: headers
forged through the active content. Therefore, suitable ACL
configurations must be implemented to prevent connections to web
sites that might host malicious content.