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 cookies.xml
Date Tue, 03 Jun 2003 21:26:35 GMT
olegk       2003/06/03 14:26:35

  Modified:    httpclient/xdocs cookies.xml
  Log:
  Minor corrections in the Cookies guide
  
  Contributed by Oleg Kalnichevski
  
  Revision  Changes    Path
  1.2       +46 -26    jakarta-commons/httpclient/xdocs/cookies.xml
  
  Index: cookies.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/httpclient/xdocs/cookies.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- cookies.xml	1 Jun 2003 18:51:23 -0000	1.1
  +++ cookies.xml	3 Jun 2003 21:26:35 -0000	1.2
  @@ -5,6 +5,7 @@
     <properties>
       <title>HttpClient Cookie Guide</title>
       <author email="adrian@intencha.com">Adrian Sutton</author>
  +    <author email="oleg@ural.ru">Oleg Kalnichevski</author>
       <revision>$Id$</revision>
     </properties>
   
  @@ -16,20 +17,32 @@
         server when required.  It is also possible to manually set cookies to be
         sent to the server.</p>
   
  -      <p>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.</p>
  +      <p>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.</p>
       </section>
   
       <section name="Available Specifications">
         <p>The following cookie specifications are supported by HttpClient.</p>
   
  +      <subsection name="Netscape Draft">
  +        <p>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.</p>
  +
  +        <p>The Netscape cookie draft is available at <a
  +        href="http://wp.netscape.com/newsref/std/cookie_spec.html">http://wp.netscape.com/newsref/std/cookie_spec.html</a>
  +        </p>
  +      </subsection>
  +
         <subsection name="RFC2109">
  -        <p>RFC2109 is the final published specification released by the W3C.
  -        Theoretically, all servers that handle cookies should use this
  +        <p>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.</p>
   
  @@ -43,23 +56,31 @@
           </p>
         </subsection>
   
  -      <subsection name="Netscape Draft">
  -        <p>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.</p>
  -
  -        <p>The Netscape cookie draft is available at <a
  -        href="http://wp.netscape.com/newsref/std/cookie_spec.html">http://wp.netscape.com/newsref/std/cookie_spec.html</a>
  -        </p>
  -      </subsection>
  -
         <subsection name="Compatibility">
           <p>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.</p>
         </subsection>
  +
  +    </section>
  +
  +    <section name="Unsupported Specifications">
  +      <p>The following cookie specifications are not presently supported by HttpClient.</p>
  +
  +      <subsection name="RFC2965">
  +        <p>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.</p>
  +
  +        <p>Currently HttpClient does not implement this specification. Support for
  +           version 2 cookies will be added in the future</p>
  +
  +        <p>RFC2965 is available at
  +        <a href="http://www.w3.org/Protocols/rfc2965/rfc2965.txt">http://www.w3.org/Protocols/rfc2965/rfc2965.txt</a>
  +        </p>
  +      </subsection>
  +      
       </section>
   
       <section name="Specifying the Specification">
  @@ -91,17 +112,16 @@
           of:</p>
   
           <ul>
  -          <li><code>String.valueOf(CookiePolicy.COMPATIBILITY)</code></li>
  -          <li><code>String.valueOf(CookiePolicy.NETSCAPE_DRAFT)</code></li>
  -          <li><code>String.valueOf(CookiePolicy.RFC2109)</code></li>
  +          <li><code>"COMPATIBILITY"</code></li>
  +          <li><code>"NETSCAPE_DRAFT"</code></li>
  +          <li><code>"RFC2109"</code></li>
           </ul>
   
           <p>This setting will be used by any newly created HttpState objects,
           however existing HttpState instances will not be affected.</p>
   
           <source>
  -        System.setProperty("apache.commons.httpclient.cookiespec",
  -        String.valueOf(CookiePolicy.COMPATIBILITY));
  +        System.setProperty("apache.commons.httpclient.cookiespec", "COMPATIBILITY");
           </source>
         </subsection>
       </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