Index: cookies.xml =================================================================== RCS file: /home/cvs/jakarta-commons/httpclient/xdocs/cookies.xml,v retrieving revision 1.3 diff -u -r1.3 cookies.xml --- cookies.xml 21 Jul 2003 13:05:03 -0000 1.3 +++ cookies.xml 2 Nov 2003 19:09:23 -0000 @@ -56,13 +56,18 @@
-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 cookies, you should probably try using this specification.
This cookie specification ignores all cookies. It should be used to + keep HttpClient from accepting and sending cookies.
+There is two ways to specify which cookie specification should be - used, either for each HttpState instance, or by setting the default for - newly created HttpState instances.
- -In most cases, the best way to set which cookie specification to use
- is using the setCookiePolicy(int policy) method on
- HttpState. Any HttpClient using that HttpState will then
- use the specified cookie policy. The value of policy
- should be one of:
CookiePolicy.COMPATIBILITYCookiePolicy.NETSCAPE_DRAFTCookiePolicy.RFC2109There are two ways to specify which cookie specification should be
+ used, either for each HttpMethod instance using the
+ HttpMethodParams, or by setting the default value on
+ CookiePolicy.
In most cases, the best way to specify the cookie spec to use is the
+ setCookiePolicy(String policy) method on
+ HttpMethodParams. The value of policy
+ must be one of the values registered with CookiePolicy.registerCookieSpec().
The default cookie specification can be set by setting the system
- property apache.commons.httpclient.cookiespec to one
- of:
"COMPATIBILITY""NETSCAPE_DRAFT""RFC2109"This setting will be used by any newly created HttpState objects, - however existing HttpState instances will not be affected.
+The default cookie specification can be set by defining the default cookie
+ policy on CookiePolicy.