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

Part Number E18782-01
Go to Documentation Home
Go to Table of Contents
Go to Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
View PDF

2 Known Issues

This chapter lists the important known issues and limitations at the time of the Proxy Server 4.0.16 release.

The issues are grouped under the following categories:

2.1 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


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


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.


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


Proxy Server administration interface is not localized.


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 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 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.


  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 Proxy Server with JRE 1.4.2_13. For HP-UX, run Proxy Server with JRE


On Windows, a server identifier with multibyte characters causes server-side createInstance.exe error.


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.


Backslashes should be used in LDAP UIDs only to escape special characters. The ldap sdk used by the 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).


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

2.2 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


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


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.


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

The error messages can be ignored.


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

When 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 Proxy Server-specific headers such as Proxy-authorization.


Do not select NCA in the Proxy Listen Socket setting.

2.3 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


Windows console installation fails.


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


Silent upgrade installation does not work.


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


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.


On Windows, uninstalling the patch does not change the 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 Proxy Server release due to the RenameService.exe utility limitations. Therefore, even after uninstalling the patch, the service description shows the latest Proxy Server release instead of the previous release number.

2.4 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


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


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


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


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.


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.


Proxy Server's content rewriting function is inconsistent.

6526476 and 6526488

In a standalone installation of 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).


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.


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

HTTP7774: received extraneous data following response

2.5 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


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


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


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

2.6 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


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.


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


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 Proxy Server.