commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ol...@apache.org
Subject cvs commit: jakarta-commons/httpclient/xdocs sslguide.xml
Date Thu, 15 Apr 2004 21:07:45 GMT
olegk       2004/04/15 14:07:45

  Modified:    httpclient/xdocs sslguide.xml
  Log:
  SSL guide amendments
  
  Contributed by Oleg Kalnichevski, Daniel C. Amadei <daniel.amadei at click21.com.br>,
Eric Johnson <eric at tibco.com>
  
  Revision  Changes    Path
  1.4       +38 -1     jakarta-commons/httpclient/xdocs/sslguide.xml
  
  Index: sslguide.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/httpclient/xdocs/sslguide.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- sslguide.xml	21 Aug 2003 16:08:54 -0000	1.3
  +++ sslguide.xml	15 Apr 2004 21:07:45 -0000	1.4
  @@ -240,6 +240,43 @@
           </p>
           </li>
   
  +        <li>
  +        <p>
  +         <strong>JSSE prior to Java 1.4 incorrectly reports socket timeout.</strong>
  +        </p>
  +        <p>
  +         Prior to Java 1.4, in Sun's JSSE implementation, a read operation that has timed
out incorrect
  +         reports end of stream condition instead of throwing java.io.InterruptedIOException
as expected.
  +         HttpClient responds to this exception by assuming 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".
  +         It should instead report "java.io.InterruptedIOException: Read timed out". If
you see the "unable to find
  +         line..." 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>Work-around:</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>
  +         Several releases of the IBM JSSE exhibit a bug that cause 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. HttpClient users
  +         have reported that IBM Websphere Application Server versions 4.0.6, 5.0.2.2, 5.1
do not exhibit the problem.
  +        </p>
  +        </li>
         </ol>
    
       </section>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message