Return-Path: 
 <commons-dev-return-64340-apmail-jakarta-commons-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org
Received: (qmail 50979 invoked from network); 13 Dec 2004 21:52:52 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 13 Dec 2004 21:52:52 -0000
Received: (qmail 83796 invoked by uid 500); 13 Dec 2004 21:52:49 -0000
Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org
Received: (qmail 83747 invoked by uid 500); 13 Dec 2004 21:52:49 -0000
Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:commons-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:commons-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:commons-dev-help@jakarta.apache.org>
List-Post: <mailto:commons-dev@jakarta.apache.org>
List-Id: "Jakarta Commons Developers List" <commons-dev.jakarta.apache.org>
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Delivered-To: mailing list commons-dev@jakarta.apache.org
Received: (qmail 83730 invoked by uid 500); 13 Dec 2004 21:52:49 -0000
Received: (qmail 83726 invoked by uid 99); 13 Dec 2004 21:52:49 -0000
X-ASF-Spam-Status: No, hits=-10.0 required=10.0
	tests=ALL_TRUSTED,NO_REAL_NAME
X-Spam-Check-By: apache.org
Received: from minotaur.apache.org (HELO minotaur.apache.org)
 (209.237.227.194)
  by apache.org (qpsmtpd/0.28) with SMTP; Mon, 13 Dec 2004 13:52:48 -0800
Received: (qmail 50917 invoked by uid 1624); 13 Dec 2004 21:52:47 -0000
Date: 13 Dec 2004 21:52:47 -0000
Message-ID: <20041213215247.50916.qmail@minotaur.apache.org>
From: olegk@apache.org
To: jakarta-commons-cvs@apache.org
Subject: cvs commit: jakarta-commons/httpclient/xdocs sslguide.xml
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

olegk       2004/12/13 13:52:47

  Modified:    httpclient/xdocs Tag: HTTPCLIENT_2_0_BRANCH sslguide.xml
  Log:
  *  AuthSSLProtocolSocketFactory description
  * "Known limitations and problems" section amended
  
  Revision  Changes    Path
  No                   revision
  No                   revision
  1.2.2.4   +9 -3      jakarta-commons/httpclient/xdocs/sslguide.xml
  
  Index: sslguide.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/httpclient/xdocs/sslguide.xml,v
  retrieving revision 1.2.2.3
  retrieving revision 1.2.2.4
  diff -u -r1.2.2.3 -r1.2.2.4
  --- sslguide.xml	11 May 2004 21:46:38 -0000	1.2.2.3
  +++ sslguide.xml	13 Dec 2004 21:52:47 -0000	1.2.2.4
  @@ -183,6 +183,11 @@
            <a href="http://cvs.apache.org/viewcvs.cgi/jakarta-commons/httpclient/src/contrib/org/apache/commons/httpclient/contrib/ssl/?only_with_tag=HTTPCLIENT_2_0_BRANCH">  
             StrictSSLProtocolSocketFactory</a> can be used to create SSL connections that can optionally perform host name verification in order to help preventing man-in-the-middle type of attacks. 
           </li>
  +        <li>
  +         <a href="http://cvs.apache.org/viewcvs.cgi/jakarta-commons/httpclient/src/contrib/org/apache/commons/httpclient/contrib/ssl/?only_with_tag=HTTPCLIENT_2_0_BRANCH">  
  +          AuthSSLProtocolSocketFactory</a> can be used to optionally enforce mutual client/server authentication. This is the most flexible
  +          implementation of a protocol socket factory.  It allows for customization of most, if not all, aspects of the SSL authentication.
  +        </li>
   
         </ul>
       
  @@ -273,8 +278,9 @@
            "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.
  +         <strong>Solution:</strong> Make sure that you have all the latest Websphere fix packs applied and IBMJSSE
  +         is at least version 1.0.3. HttpClient users have reported that IBM Websphere Application Server versions 
  +         4.0.6, 5.0.2.2, 5.1.0 and above do not exhibit this problem.
           </p>
           </li>
         </ol>
  
  
  

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