On Sun, 2011-01-09 at 15:03 +0000, sebb wrote: > On 9 January 2011 11:38, Oleg Kalnichevski <[email protected]> wrote: > > On Sat, 2011-01-08 at 08:34 +0100, Magnus Leuthner wrote: > >> Hello developers, > >> > >> I've tried to use httpclient 3.x and 4.x with www.hotelextranet.com and > >> from > >> what I observe it always seems to get the cookie format wrong. > > > > The cookie is question violates the HTTP state management specification > > > >> The cookies > >> end up garbled unless I specifically set the "NETSCAPE" standard. The > >> "BESTFIT" of 4.x doesn't seem to be the best fit for this IIS6 server. The > >> headers are (anonymized): > > That's because there is no "expires" qualifier for the user cookie. > > The "expires" qualifier is unique to Netscape cookies, and is used to > identify them. >
The "expires" attribute was defined as optional by the Netscape draft. Therefore, there can always be ambiguity as to whether or not a particular cookie conforms to the original draft document. Netscape style cookies are inherently ambiguous and there is simply no excuse to continue using them, especially on the server side, especially by companies like Microsoft. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
