Index: /home/oleg/src/apache.org/jakarta-commons/httpclient-trunk/xdocs/troubleshooting.xml =================================================================== --- /home/oleg/src/apache.org/jakarta-commons/httpclient-trunk/xdocs/troubleshooting.xml (revision 180130) +++ /home/oleg/src/apache.org/jakarta-commons/httpclient-trunk/xdocs/troubleshooting.xml (working copy) @@ -39,6 +39,12 @@ communication between the client and server to determine where the problem is occurring. +
+ Authetication schemes that rely on persistent connection state do not work on Sun's JVMs + below 1.4 if SSL is used +
++ For details please refer to the Known + limitations and problems section of the SSL Guide +
++ Workaround: Disable stale connection check or upgrade to Java 1.4 or above. +
+Some authentication schemes may use cryptographic algorithms. It is recommended to include the Index: /home/oleg/src/apache.org/jakarta-commons/httpclient-trunk/xdocs/sslguide.xml =================================================================== --- /home/oleg/src/apache.org/jakarta-commons/httpclient-trunk/xdocs/sslguide.xml (revision 180130) +++ /home/oleg/src/apache.org/jakarta-commons/httpclient-trunk/xdocs/sslguide.xml (working copy) @@ -240,10 +240,31 @@
- Workaround: If persistent SSL connections support is an issue for your - application we strongly advise you to upgrade to Java 1.4. + Workaround: Disable stale connection check if upgrade to Java 1.4 or above is + not an option. Please note that HttpClient will no longer be able to detect invalid connections + and some requests may fail due to transport errors. For details on how transport errors can be + recovered from please refer to the + Exception Handling Guide. If persistent SSL connections support and transport reliability + is an issue for your application we strongly advise you to upgrade to Java 1.4.
++ Authetication schemes that rely on persistent connection state do not work on Sun's JVMs + below 1.4 if SSL is used +
++ This problem is directly related to the problem described above. Certain authentication schemes or + certain implementations of standard authentication schemes are connection based, that is, the user + authentication is performed once when the connection is being established, rather than every time + a request is being processed. Microsoft NTLM scheme and Digest scheme as implemented in Microsoft + Proxy and IIS servers are known to fall into this category. If connections cannot be kept alive + the user authorization is lost along with the persistent connection state +
++ Workaround: Disable stale connection check or upgrade to Java 1.4 or above. +
+