Folks,
Daniel C. Amadei has kindly contributed a paragraph on recently
discovered problem with bogus error messages caused by a bug in older
versions of Sun JSSE
I have also long promised to write a few words regarding the known
problems with IBM JSSE
Please let me know what you think. I would also like to kindly ask
someone of our resident native English speakers to proof-read the
writing
Cheers,
Oleg
PS: Daniel, I changed your original text somewhat. Please let me know if
you agree with the changes
Index: sslguide.xml
===================================================================
RCS file: /home/cvspublic/jakarta-commons/httpclient/xdocs/sslguide.xml,v
retrieving revision 1.2.2.1
diff -u -r1.2.2.1 sslguide.xml
--- sslguide.xml 21 Aug 2003 16:07:31 -0000 1.2.2.1
+++ sslguide.xml 14 Apr 2004 20:47:48 -0000
@@ -240,6 +240,45 @@
</p>
</li>
+ <li>
+ <p>
+ <strong>Socket timeout not correctly reported when using oder versions of JSSE
+ (prior to Java 1.4)</strong>
+ </p>
+ <p>
+ There is a bug in older versions of Sun JSSE that causes timed out read operation to report end of
+ stream condition instead of throwing java.io.InterruptedIOException as expected. As a result if read
+ operation on a secure (SSL) connection times out (SO_TIMEOUT is set to a positive value) HttpClient
+ mistakingly assumes that the connection was dropped and throws a recoverable HTTP exception: Error in
+ parsing the status line from the response: unable to find line starting with "HTTP" instead of
+ "java.io.InterruptedIOException: Read timed out" as expected. If you get this message when working with
+ an older version of JDK and JSSE, it can be caused by the timeout waiting for data and not by a problem
+ with the connection.
+ </p>
+ <p>
+ <strong>Solution:</strong> One possible solution is to increase the timeout value as the server is
+ taking too long to start sending the response. Alternatively you may choose to upgrade to Java 1.4 or
+ above which does not exhibit this problem.
+ </p>
+ <p>
+ The problem has been discovered and reported by Daniel C. Amadei.
+ </p>
+ </li>
+
+ <li>
+ <p>
+ <strong>HttpClient does not work with IBM JSSE shipped with IBM Websphere Application Platform</strong>
+ </p>
+ <p>
+ There is a bug in several releases of IBM JSSE that causes HttpClient to fail while detecting the size
+ of the socket send buffer (java.net.Socket.getSendBufferSize method throws java.net.SocketException:
+ "Socket closed" exception).
+ </p>
+ <p>
+ <strong>Solution:</strong> Make sure that you have all the latest fix packs applied. IBM Websphere
+ Application Server versions 4.0.6, 5.0.2.2, 5.1 have been reported to not exhibit the problem.
+ </p>
+ </li>
</ol>
</section>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
