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 martin.panter
Recipients Tim.Graham, martin.panter
Date 2015-10-03.05:13:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1443849190.04.0.309054368267.issue25228@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks for the test case. It looks like the commit in question was done as a security fix in 3.2.6 and 3.3.6. I’m not sure on the policy, but maybe that justifies putting any fixes into 3.2+.

I’m not familiar with HTTP cookies. Is this a case of a 100% specification-compiliant cookie, or a technically invalid one that would be nice to handle better? If the second case, maybe it is an instance of Issue 22983.
History
Date User Action Args
2015-10-03 05:13:10martin.pantersetrecipients: + martin.panter, Tim.Graham
2015-10-03 05:13:10martin.pantersetmessageid: <1443849190.04.0.309054368267.issue25228@psf.upfronthosting.co.za>
2015-10-03 05:13:10martin.panterlinkissue25228 messages
2015-10-03 05:13:09martin.pantercreate