At http://www.netscape.com/newsref/std/cookie_spec.html, the spec states: This string is a sequence of characters excluding semi-colon, comma and white space. If there is a need to place such data in the name or value, some encoding method such as URL style %XX encoding is recommended, though no encoding is defined or required. IMHO, this is a shortcoming of the HTTP cookie spec, in that it does not require the RFC 1738, section 2.2, encoding for cookie values. At least the spec does contain a disclaimer at the top: Preliminary Specification - Use with caution 8-) On Monday 02 July 2001 10:25 am, Olaf Walkowiak wrote: > There is a bug in HTCookie.c > If the Cookie value contains a "," all the stuff after it is > lost. This happens because the Cookie is parsed with HTNextField(). > > > > Regards > Olaf -- _______________________________________________________ James D. Brown, President, Shopswell, Inc. Voice: 303-400-0480 - FAX: 303-400-7181 http://www.shopswell.com - jamesbrown@shopswell.comReceived on Tuesday, 3 July 2001 03:49:01 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 23 April 2007 18:18:39 GMT