Regarding "There is a comma in Max-Age/expires field", while I see that there is a comma in the Netscape Expires value (Expires did not make it to RFC level), I do not see how there could be a comma in Max-Age. Specifically, both RFC 2109 says "The Max-Age attribute defines the lifetime of the cookie, in seconds. The delta-seconds value is a decimal non-negative integer" and RFC 2965 says "The value of the Max-Age attribute is delta-seconds, the lifetime of the cookie in seconds, a decimal non-negative integer."
I also notice that the Netscape spec uses a semi-colon to separate name=value pairs within the cookie, which is how it can handle the comma embedded in the value for Expires. It is not obvious how to determine that a Set-Cookie header follows the Netscape spec rather than RFC 2109. The code can try to apply 2109, and if there appear to be invalid attributes, try parsing it by the Netscape spec. I am curious, do you know of any servers that use the Netscape Set-Cookie syntax other than old versions of Netscape? Scott Nichol ----- Original Message ----- From: "Remus Stratulat" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: "Scott Nichol" <[EMAIL PROTECTED]> Sent: Wednesday, July 10, 2002 7:34 AM Subject: Re: cookies > I have a proposal for Cookie.jar > I do not know what is the proper format or way to propose a change for a > file so I attached here the code that I modified from Cookie.jar along > with comments that explains the changes. > > Remus Stratulat > > -- > /** > * Remus Stratulat - KrysalIDE maintainer > * InterAkt Online. > * > * @phone +40 90 07 24 07 > * @email [EMAIL PROTECTED] > * @web http://www.interakt.ro > */ > > ---------------------------------------------------------------------------- ---- > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
