Index: sslguide.xml =================================================================== RCS file: /home/cvs/jakarta-commons/httpclient/xdocs/sslguide.xml,v retrieving revision 1.1 diff -u -r1.1 sslguide.xml --- sslguide.xml 12 Jun 2003 03:31:50 -0000 1.1 +++ sslguide.xml 12 Jun 2003 08:48:09 -0000 @@ -16,7 +16,7 @@ HttpClient provides full support for HTTP over Secure Sockets Layer (SSL) or IETF Transport Layer Security (TLS) protocols by leveraging the Java Secure Socket Extension (JSSE). JSSE has been integrated into the Java 2 platform as of - version 1.4 and usually should work with HttpClient out of the box. On older Java 2 versions JSSE + version 1.4 and works with HttpClient out of the box. On older Java 2 versions JSSE needs to be manually installed and configured. Installation instructions can be found here

@@ -25,7 +25,7 @@

- With SSL properly set up and configured, secure HTTP communication over SSL should be as simple + Once you have JSSE correctly installed, secure HTTP communication over SSL should be as simple as plain HTTP communication.

HTTPS communication via an authenticating proxy server is also no different from plain HTTP - communication. All the low-level details of establishing a tunneled SSL connection are abstracted - away by HttpClient: + communication. All the low-level details of establishing a tunneled SSL connection are handled + by HttpClient:

- Per default HTTP client does not perform any custom certificate or certificate chain validation. - The default HTTPS protocol implementation is completely reliant upon the standard functionality - of the JSSE that comes with the JVM. If your application requires some additional processing of - credentials such certificate verification or certificate chain validation, or you want to be using - a third party SSL library, you can augment HttpClient to meet your specific requirements by providing - a custom protocol implementation. -

+ The default behaviour of HttpClient is suitable for most uses, however + there are some aspects which you may want to configure. The most common + requirements for customizing SSL are:

+ + + +

+ Implementation of a custom protocol involves the following steps: +

-

- Implementation of a custom protocol involves the following steps: -

+
    - +
-
+ -
- -

- There are several custom socket factories available in our contribution package. They can - be a good start for those who seek to tailor the behavior of the HTTPS protocol to the specific - needs of their application: -

+
+ +

+ There are several custom socket factories available in our contribution + package. They can be a good start for those who seek to tailor the + behavior of the HTTPS protocol to the specific needs of their + application: +

-