This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author aclover
Recipients BM, BreamoreBoy, aclover, akuchling, carsten.klein, dstanek, georg.brandl, jerry.seutter, jjlee, karlcow, r.david.murray, tim.peters
Date 2011-01-29.16:53:47
SpamBayes Score 0.0031491134
Marked as misclassified No
Message-id <1296320028.41.0.156383470149.issue2193@psf.upfronthosting.co.za>
In-reply-to
Content
@carsten.klein: there is no such thing as an “original RFC”. The RFCs that have been produced on the subject of cookies, 2109 and 2965, were drawn up long after user-agents implemented cookies. Their attempts to clean up the warts of cookies and implement new features have completely failed. Their strictures are not obeyed by user agents; they are irrelevant and should not be used as the basis for any server-side cookie implementation.

The nearest to an original standard for cookies is the Netscape cookie-spec (see eg http://curl.haxx.se/rfc/cookie_spec.html), which is far too woolly to really count as a real specification, but which allows all but `;`, `,` and space, and in practice browsers do typically allow all characters that do not already serve as delimiters. Python should be liberal in what it accepts.
History
Date User Action Args
2011-01-29 16:53:48acloversetrecipients: + aclover, tim.peters, akuchling, georg.brandl, jjlee, dstanek, jerry.seutter, BM, r.david.murray, karlcow, BreamoreBoy, carsten.klein
2011-01-29 16:53:48acloversetmessageid: <1296320028.41.0.156383470149.issue2193@psf.upfronthosting.co.za>
2011-01-29 16:53:47acloverlinkissue2193 messages
2011-01-29 16:53:47aclovercreate