Martin Panter added the comment:

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.

----------
keywords: +3.2regression
nosy: +martin.panter
stage:  -> needs patch

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25228>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to