➜

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 spookylukey
Recipients georg.brandl, karlcow, keakon, spookylukey, terry.reedy
Date 2013-03-09.20:28:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1362860922.99.0.808694593552.issue17340@psf.upfronthosting.co.za>
In-reply-to
Content 
I'm a core developer on Django, and I've looked into cookies a lot, and also Python's SimpleCookie, and I've found that all accepted RFCs are completely irrelevant for this issue.

No accepted RFC was ever widely implemented - instead browsers mainly did something like the original "Netscape cookies", with various interpretations. Opera attempted RFC 2965, at least at one point, but no-one else.

RFC 6265, whatever its status, is probably the closest thing to a useful document of how cookies "should" work. But even then, I'm afraid that the main guiding principle has to be sheer pragmatism. Read the source code or bug trackers of any other project that has to handle cookies and you'll find they have all come to that conclusion, unfortunately.
History
Date User Action Args
2013-03-09 20:28:43spookylukeysetrecipients: + spookylukey, georg.brandl, terry.reedy, karlcow, keakon
2013-03-09 20:28:42spookylukeysetmessageid: <1362860922.99.0.808694593552.issue17340@psf.upfronthosting.co.za>
2013-03-09 20:28:42spookylukeylinkissue17340 messages
2013-03-09 20:28:42spookylukeycreate