Skip Headers
Oracle® iPlanet Web Proxy Server Release Notes
Release 4.0.23

E18782-09
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

2 Known Issues

This chapter lists the important known issues and limitations at the time of the Oracle iPlanet Web Proxy Server 4.0.19 release.

This chapter contains the following sections:

2.1 Oracle iPlanet Web Proxy Server 4.0 Administration Issues

Table 2-1 lists the known issues related to the administration user interface.

Table 2-1 Known Issues in Administration

Issue ID Summary

6653507

If Monitor Current Activity Statistics/Profiling is set to ON, it cannot be turned OFF from the user's interface.

6212701

Conflicting error messages are displayed when server instance fails to start.

The chances of occurrence of the conflicting error messages are minimal because the chances of the administration interface writing wrong information in the configuration file is minimal. It can occur only if the user manually writes wrong information into the configuration file.

6231297

The Restart Required link disappears if changes are made to the SOCKS configuration and Oracle iPlanet Web Proxy Server is restarted instead of the SOCKS server.

6484502

Oracle iPlanet Web Proxy Server administration interface is not localized.

6509535

Daylight Savings Time (DST) will start in U.S.A from the 2nd Sunday of March and end on the 1st Sunday of November. This will impact the date and time rules of the operating system and JRE.

In the standalone version of Oracle iPlanet Web Proxy Server, the JRE version compatible with 2007 DST changes is bundled with the installer. However, you need to address the impact on the date and time rules of the operating system by installing the appropriate operating system patches as explained in Step 1 of the Workaround.

For the Java ES 5 installation of Oracle iPlanet Web Proxy Server, you need to install the operating system patches and also the compatible version of JRE. Follow Step 1 and Step 2 of the workaround.

Workaround

  1. Download and use the appropriate operating system patches.

    For other platforms, download similar DST-compatible patches from the operating system vendor's web site.

  2. For Solaris, Windows, and Linux, run Oracle iPlanet Web Proxy Server with JRE 1.4.2_13. For HP-UX, run Oracle iPlanet Web Proxy Server with JRE 1.4.2.12.

6867774

The Administration Server fails to start when a proxy installation that uses a custom JDK configuration is upgraded to a service pack version that requires a newer JDK version. After the upgrade, the JDK configuration must be manually modified to point to either the bundled JDK or a custom JDK of the required version.

6909558

Backslashes should be used in LDAP UIDs only to escape special characters. The ldap sdk used by the Oracle iPlanet Web Proxy Server will remove backslashes from the UID before sending the same to the directory server. This can possibly lead to a situation where the authentication fails where it should succeed (because the UID, with backslashes stripped, finds no match in the directory server), or even succeeds where it should fail (because the UID, with backslashes stripped, finds a match in the directory server).

6888170

Upgrade fails on RHEL4 when the specified target directory name contains a trailing slash.

12307267

Fails to migrate from Oracle iPlanet Web Proxy Server 3.6 to Oracle iPlanet Web Proxy Server 4.0 with Security Sockets Layer (SSL) configuration.

Currently, Web Proxy 3.6 certificates cannot be migrated to a Web Proxy 4.0 instance.

Workaround:

  1. Turn off the security option in the Oracle iPlanet Web Proxy Server 3.6 instance.

  2. Migrate from Oracle iPlanet Web Proxy Server 3.6 to 4.0.

  3. Generate a certificate signing request (CSR).

  4. Create and install certificates to enable security on the Oracle iPlanet Web Proxy Server 4.0 instance.


2.2 Oracle iPlanet Web Proxy Server 4.0 Caching Issues

Table 2-2 lists the known issues related to caching.

Table 2-2 Known Issues in Caching

Issue ID Summary

6654514

Proxy-agent header displays the original header for request type 504.

6229823

When a new partition is added, a default section s0.0 is also created irrespective of the partition size. Warning messages are logged in the errors file.

Workaround

Use the cbuild utility to add the new partition or delete the s0.0 folder under the new cache partition, and restart Oracle iPlanet Web Proxy Server.

The error messages can be ignored.

6619620

Doc RFE: Oracle iPlanet Web Proxy Server should not be used with Network Cache Accelerator (NCA).

When Oracle iPlanet Web Proxy Server 4.0.8 is used with NCA, a browser repeatedly prompts for the User ID and password. This happens because NCA does not support Oracle iPlanet Web Proxy Server-specific headers such as Proxy-authorization.

Workaround

Do not select NCA in the Proxy Listen Socket setting.


2.3 Oracle iPlanet Web Proxy Server 4.0 Installation Issues

Table 2-3 lists the known issues related to installation.

Table 2-3 Known Issues in Installation

Issue ID Summary

6205683

Windows console installation fails.

6255325

The installer throws an exception and the installation fails on Linux if the user installs Oracle iPlanet Web Proxy Server as a non root user and the /var/opt/sun/install directory does not exist.

6353576

Silent upgrade installation does not work.

6587776

Oracle iPlanet Web Proxy Server from Java ES 5 on Windows XP displays system error 1067.

6756659

Oracle iPlanet Web Proxy Server 4.0.9 can be installed on OpenSolaris by using the GUI installer only if the --javahome option of the setup command is used to specify a JDK 1.6 location.

6607551

On Windows, uninstalling the patch does not change the Oracle iPlanet Web Proxy Server release to the previous release number.

Reverting the patch through the Uninstaller script does not change the service description name to the previous Oracle iPlanet Web Proxy Server release due to the RenameService.exe utility limitations. Therefore, even after uninstalling the patch, the service description shows the latest Oracle iPlanet Web Proxy Server release instead of the previous release number.

12951802

Fix CR:6932016-Verisign EV cert chain issue with newly built in CA root 4.0.16

Workaround

If you are using Verisign EV 2048-bit SSL web proxy server certificates, some older browsers may have "Certificate Authority Not Trusted" warning after you upgrade from web proxy 4.x.x prior versions to web proxy 4.x.x update or later. Follow these steps to overcome this problem:

  1. Stop the web proxy server.

  2. Execute cd <proxy instance dir>/config

  3. To list the Root Certs module, execute modutil -list -nocertdb -dbdir

  4. Execute modutil -dbdir . -delete 'Root Certs'

  5. Execute modutil -list -nocertdb -dbdir

    The Root Certs module is removed.

  6. Start the web proxy server.

    If you upgrade to a higher version once the above process is implemented, make sure to follow the same process in the upgraded version as well.


2.4 Oracle iPlanet Web Proxy Server 4.0 Internationalization Issues

Table 2-4 lists the known issues related to internationalization.

Table 2-4 Known Issues in Internationalization

Issue ID Summary

6233080

The Disable Proxying option does not work for the URL with multibyte data (URL encoded) when routing is set through another proxy server.

6233090

A URL with multibyte data (URL encoded) cannot be mapped.

6253844

Oracle iPlanet Web Proxy Server online help does not support the language zh-cn.

6297168

Starting the server in a different system encoding causes any errors returned by that particular system to be logged in the error log. When viewed through the Administration Server, the error log might have characters in the system encoding that do not display properly.

Workaround

Change the browser encoding to match the OS locale so that the error log can be properly viewed through the administration interface. But this will be needed every time you move to other pages and then return to View Error Log.

6300080

Oracle iPlanet Web Proxy Server's content rewriting function is inconsistent.

6526476 and 6526488

In a standalone installation of Oracle iPlanet Web Proxy Server on HP-UX, the installation in GUI mode results in the display of corrupted Japanese characters (ID no. 6526476). If the installation is continued, it results in error while creating an instance (ID no. 6526488).

Workaround

You can use either of the following workarounds:

  • Use the CLI mode of installation for Japanese locale on HP-UX.

  • Continue the installation even with the corrupted display of characters. When the installer fails to create an instance, log in to the administration interface and create an instance.

6550995

The following error message is not localized for all the locales:

HTTP7774: received extraneous data following response


2.5 Oracle iPlanet Web Proxy Server 4.0 Localization Issues

Table 2-5 lists the know issues related to Localization.

Table 2-5 Known Issues in Localization

Issue ID Summary

6779070

The Oracle iPlanet Web Proxy Server online help has broken links for Terms of Use.

6253844

The set language option in the Oracle iPlanet Web Proxy Server online help does not support the language zh-cn.

6828246

The Korean characters are not displayed in the Oracle iPlanet Web Proxy Server installer on RHEL 5.2.


2.6 Oracle iPlanet Web Proxy Server 4.0 SOCKS Issues

Table 2-6 lists the known issues related to SOCKS.

Table 2-6 Known Issues in SOCKS

Issue ID Summary

6245453

The Quench Updates feature is shown in the GUI and documented for the Server Manager > SOCKS > Configure SOCKS v5 page, but the feature is not implemented.

6263389

No error is reported when two instances of SOCKS are started using the same port on Windows.

6285791

SOCKS server start command-line issue for Java ES 4 is resolved in release 4.0.5, but existing instances created in Java ES 4 installation will have the problem even after upgrading to the latest 4.0.3 patches. The new instances created after upgrade will not have this problem. This problem is not there in a standalone installation of Oracle iPlanet Web Proxy Server.