Message 183789 - Python tracker

➜

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	keakon
Recipients	georg.brandl, keakon, spookylukey, terry.reedy
Date	2013-03-09.03:31:55
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1362799915.38.0.0572022882244.issue17340@psf.upfronthosting.co.za>
In-reply-to

Content
Terry, say that a user's cookie is ",BRIDGE_R=; a=b;" right now. When he login, the server sends "Set-Cookie: user_id=1; Path=/" header to him. Then his cookie is ",BRIDGE_R=; a=b; user_id=1;" now. The next time he sends cookie to the server, Cookie.SimpleCookie.load() tries to parse the cookie, but raises a CookieError. So the server has no way to get his user_id from cookie. It has to let him login again and sends "Set-Cookie: user_id=1; Path=/" header infinitely. I cannot clear all cookies because Cookie.SimpleCookie.load() even dosen't let me know the keys in his cookie.

Terry, say that a user's cookie is ",BRIDGE_R=; a=b;" right now.
When he login, the server sends "Set-Cookie: user_id=1; Path=/" header to him.
Then his cookie is ",BRIDGE_R=; a=b; user_id=1;" now.

The next time he sends cookie to the server, Cookie.SimpleCookie.load() tries to parse the cookie, but raises a CookieError.
So the server has no way to get his user_id from cookie. It has to let him login again and sends "Set-Cookie: user_id=1; Path=/" header infinitely.

I cannot clear all cookies because Cookie.SimpleCookie.load() even dosen't let me know the keys in his cookie.

History
Date	User	Action	Args
2013-03-09 03:31:55	keakon	set	recipients: + keakon, georg.brandl, terry.reedy, spookylukey
2013-03-09 03:31:55	keakon	set	messageid: <1362799915.38.0.0572022882244.issue17340@psf.upfronthosting.co.za>
2013-03-09 03:31:55	keakon	link	issue17340 messages
2013-03-09 03:31:55	keakon	create