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 karlcow
Recipients BM, BreamoreBoy, aclover, akuchling, dstanek, georg.brandl, jerry.seutter, jjlee, karlcow, r.david.murray, tim.peters
Date 2011-01-05.06:06:27
SpamBayes Score 1.0079489e-05
Marked as misclassified No
Message-id <1294207589.63.0.816928877108.issue2193@psf.upfronthosting.co.za>
In-reply-to
Content
The rules for parsing and setting the cookies are different. Server should always produce strict cookies only. So the production rules are to be done accordingly to the specification.

Adam Barth is working right now on an update of the  "HTTP State Management Mechanism" specification. See http://tools.ietf.org/html/draft-ietf-httpstate-cookie

The name production rules are still defined in RFC2696

What browsers ignores or not in characters depends from browsers to browsers. (IETF server is down right now, and I can't link to the appropriate section for parsing the values.)
History
Date User Action Args
2011-01-05 06:06:30karlcowsetrecipients: + karlcow, tim.peters, akuchling, georg.brandl, jjlee, dstanek, jerry.seutter, BM, aclover, r.david.murray, BreamoreBoy
2011-01-05 06:06:29karlcowsetmessageid: <1294207589.63.0.816928877108.issue2193@psf.upfronthosting.co.za>
2011-01-05 06:06:27karlcowlinkissue2193 messages
2011-01-05 06:06:27karlcowcreate