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 orsenthil
Recipients BM, BreamoreBoy, aclover, akuchling, carsten.klein, dstanek, georg.brandl, jerry.seutter, jjlee, karlcow, orsenthil, r.david.murray, serhiy.storchaka, spookylukey, tim.peters
Date 2012-04-16.15:29:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1334590155.83.0.0520010857749.issue2193@psf.upfronthosting.co.za>
In-reply-to
Content
I tested setting cookies with ":" in the cookie name in both firefox and google-chrome. They both seem to allow and store the cookie with ":" in them.
Firefox sent a request header like this:

Set-Cookie	test:value=solution:is:he

the cookie with name containing ; or , failed.

The patched attached tries to silence the error with SimpleCookie. I am not sure how far it is going to help. I believe, we could just allow it from 3.3 onwards or create a new BrowserCookie class which is more lenient than SimpleCookie.

As far I see, the allowing ":" in the Legalchars seem to have met with negative votes because it was not in RFC, but well it seems some kind of de-facto acceptable behaviour with browsers, so having from a new version may not cause any harm. +1 to that. I can modify the tests from the attached patch.
History
Date User Action Args
2012-04-16 15:29:16orsenthilsetrecipients: + orsenthil, tim.peters, akuchling, georg.brandl, jjlee, dstanek, jerry.seutter, BM, aclover, r.david.murray, karlcow, BreamoreBoy, spookylukey, carsten.klein, serhiy.storchaka
2012-04-16 15:29:15orsenthilsetmessageid: <1334590155.83.0.0520010857749.issue2193@psf.upfronthosting.co.za>
2012-04-16 15:29:15orsenthillinkissue2193 messages
2012-04-16 15:29:15orsenthilcreate