Index: cookies.xml =================================================================== RCS file: /home/cvspublic/jakarta-commons/httpclient/xdocs/cookies.xml,v retrieving revision 1.1 diff -u -r1.1 cookies.xml --- cookies.xml 1 Jun 2003 18:51:23 -0000 1.1 +++ cookies.xml 2 Jun 2003 14:54:43 -0000 @@ -5,6 +5,7 @@ HttpClient Cookie Guide Adrian Sutton + Oleg Kalnichevski $Id: cookies.xml,v 1.1 2003/06/01 18:51:23 mbecke Exp $ @@ -16,20 +17,32 @@ server when required. It is also possible to manually set cookies to be sent to the server.

-

Unfortunately, there are two major standards for handling Cookies, - RFC2109 and the Netscape Cookie draft, and a large number of - implementations are completely non-standard. To deal with this, - HttpClient provides configurable cookie specifications. This guide will - explain how to use the different cookie specifications and identify some - of the common problems people have when using Cookies and HttpClient.

+

Unfortunately, there are several at times conflicting standards for + handling Cookies: the Netscape Cookie draft, RFC2109, RFC2965 and a large + number of vendor specific implementations that are compliant with neither + specification. To deal with this, HttpClient provides policy driven cookie + management. This guide will explain how to use the different cookie + specifications and identify some of the common problems people have when + using Cookies and HttpClient.

The following cookie specifications are supported by HttpClient.

+ +

The Netscape draft is the original cookie specification which formed + the basis for RFC2109. Despite this it has some significant + differences with RFC2109 and thus may be required for compatibility + with some servers.

+ +

The Netscape cookie draft is available at http://wp.netscape.com/newsref/std/cookie_spec.html +

+
+ -

RFC2109 is the final published specification released by the W3C. - Theoretically, all servers that handle cookies should use this +

RFC2109 is the first official cookie specification released by the W3C. + Theoretically, all servers that handle version 1 cookies should use this specification and as such this specification is used by default within HttpClient.

@@ -43,23 +56,31 @@

- -

The Netscape draft is the original cookie specification which formed - the basis for RFC2109. Despite this it has some significant - differences with RFC2109 and thus may be required for compatibility - with some servers.

- -

The Netscape cookie draft is available at http://wp.netscape.com/newsref/std/cookie_spec.html -

-
-

The compatibility specification is designed to be compatible with as many different servers as possible even if they are not completely - standards compliant. If you are encountering problems with parsing + standards compliant. If you are encountering problems with parsing cookies, you should probably try using this specification.

+ +
+ +
+

The following cookie specifications are not presently supported by HttpClient.

+ + +

RFC2965 defines cookie version 2 and attempts to address the shortcomings + of the RFC2109 regarding cookie version 1. RFC2965 is intended to eventually + supersede RFC2109.

+ +

Currently HttpClient does not implement this specification. Support for + version 2 cookies will be added in the future

+ +

RFC2965 is available at + http://www.w3.org/Protocols/rfc2965/rfc2965.txt +

+
+
@@ -91,17 +112,16 @@ of:

This setting will be used by any newly created HttpState objects, however existing HttpState instances will not be affected.

- System.setProperty("apache.commons.httpclient.cookiespec", - String.valueOf(CookiePolicy.COMPATIBILITY)); + System.setProperty("apache.commons.httpclient.cookiespec", "COMPATIBILITY");