➜

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 jjlee
Recipients BM, BreamoreBoy, akuchling, jerry.seutter, jjlee, tim.peters
Date 2010-09-21.22:32:11
SpamBayes Score 1.2643457e-07
Marked as misclassified No
Message-id <1285108334.11.0.475957922111.issue2193@psf.upfronthosting.co.za>
In-reply-to
Content 
Looks like a bug.  Here's the trac bug that this caused -- trac fixed their bug by working around this bug in a really ugly way:

http://trac.edgewall.org/ticket/2256

It would be nice to notify the trac developers if/when this is fixed.

This bug is probably not specific to colons (e.g. commas used to be valid in HTTP cookie strings, and still are as far as I know -- somebody should test what current browsers do to make sure).  The set of characters regarded as legal is less important than the fact that parsing a Cookie header should *never* raise CookieError -- it should just ignore any invalid cookies.  Still, IIRC there isn't any need to treat any of them as invalid, since more or less anything is a valid cookie (or was in the past -- as I say, maybe browsers have cleaned up since then, but I'd be surprised).
History
Date User Action Args
2010-09-21 22:32:14jjleesetrecipients: + jjlee, tim.peters, akuchling, jerry.seutter, BM, BreamoreBoy
2010-09-21 22:32:14jjleesetmessageid: <1285108334.11.0.475957922111.issue2193@psf.upfronthosting.co.za>
2010-09-21 22:32:11jjleelinkissue2193 messages
2010-09-21 22:32:11jjleecreate