[Bug] Cookie from older version
If you have an old cookie from Mailman 2.0.x, you'll have to re-login for every page until you manually clear the cookie from your browser (after upgrading to 2.1).
Is there any way to fix this in the future? With some browsers, it's not simple to remove an individual cookie.
-- "Since when is skepticism un-American? Dissent's not treason but they talk like it's the same..." (Sleater-Kinney - "Combat Rock")
29-Jan-03 at 13:37, Will Yardley (william+mm@hq.newdream.net) wrote :
If you have an old cookie from Mailman 2.0.x, you'll have to re-login for every page until you manually clear the cookie from your browser (after upgrading to 2.1).
Is there any way to fix this in the future? With some browsers, it's not simple to remove an individual cookie.
On WinBlows, you can delete individual cookies in the "Temporary Internet Files" directory.
In Netscape and clones there's usually a cookies / cookies.txt file
Opera has cookies.dat
They can be edited.
-- |-Simon White, Internet Services Manager, Certified Check Point CCSA. |-MTDS Internet, Security, Anti-Virus, Linux and Hosting Solutions. |-MTDS 14, rue du 16 novembre, Agdal, Rabat, Morocco. |-MTDS tel +212.3.767.4861 - fax +212.3.767.4863
On Thu, Jan 30, 2003 at 09:14:05AM +0000, Simon White wrote:
29-Jan-03 at 13:37, Will Yardley (william+mm@hq.newdream.net) wrote :
If you have an old cookie from Mailman 2.0.x, you'll have to re-login for every page until you manually clear the cookie from your browser (after upgrading to 2.1).
Is there any way to fix this in the future? With some browsers, it's not simple to remove an individual cookie.
On WinBlows, you can delete individual cookies in the "Temporary Internet Files" directory.
In Netscape and clones there's usually a cookies / cookies.txt file
Opera has cookies.dat
They can be edited.
I said "with *some* browsers.
Chimera on Mac OS X is one (you can edit the cookies.txt file by hand, but not from the menu AFAIK). In any event, the issue is also that many people won't know that they need to remove the cookie in the first place, and many people wouldn't know how to do it if they could.
There are people other than geeks who run, admin, or moderate lists using Mailman, y'know...
-- "Since when is skepticism un-American? Dissent's not treason but they talk like it's the same..." (Sleater-Kinney - "Combat Rock")
30-Jan-03 at 18:23, Will Yardley (william+mm@hq.newdream.net) wrote :
On Thu, Jan 30, 2003 at 09:14:05AM +0000, Simon White wrote:
29-Jan-03 at 13:37, Will Yardley (william+mm@hq.newdream.net) wrote :
Is there any way to fix this in the future? With some browsers, it's not simple to remove an individual cookie.
Terribly sorry. For "simple" I read "possible". You are right. It's rarely simple to remove a cookie.
There are people other than geeks who run, admin, or moderate lists using Mailman, y'know...
Sorry again. I'm still a newbie to this list, I haven't got the right "feel" for it yet.
p.s. Proud to be a geek. Shame some people's definition of geek is pejorative though :(
-- -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT/L/MU/P/O d+(-) s: a- C++(+++)$ ULS++>+++$ P++>+++ L+++$ E--- W++(+++)$ N !o !K w++@$ O? M+ V? PS++@ PE Y+ PGP-@ t(+)@ 5? X+ R- tv(+)@ b++ DI+ !D G- e++ h--- r+++ y++(+++) ------END GEEK CODE BLOCK------
"WY" == Will Yardley william+mm@hq.newdream.net writes:
WY> If you have an old cookie from Mailman 2.0.x, you'll have to
WY> re-login for every page until you manually clear the cookie
WY> from your browser (after upgrading to 2.1).
WY> Is there any way to fix this in the future? With some
WY> browsers, it's not simple to remove an individual cookie.This isn't a browser bug, it's a misfeature of Python's Cookie.py module, which Mailman uses. There /will/ be a fix in Mailman 2.1.1 but I haven't worked the patch out yet.
-Bary
31-Jan-03 at 00:40, Barry A. Warsaw (barry@python.org) wrote :
"WY" == Will Yardley william+mm@hq.newdream.net writes:
WY> If you have an old cookie from Mailman 2.0.x, you'll have to WY> re-login for every page until you manually clear the cookie WY> from your browser (after upgrading to 2.1). WY> Is there any way to fix this in the future? With some WY> browsers, it's not simple to remove an individual cookie.This isn't a browser bug, it's a misfeature of Python's Cookie.py module, which Mailman uses. There /will/ be a fix in Mailman 2.1.1 but I haven't worked the patch out yet.
Kinda tough if you don't have the mailman version in the cookie. A good reason to put it in there, from now on, if it isn't there.
Any other parameter in the cookie which has changed could be detected by the new version and force an expiration of the cookie immediately so that the problem will go away.
-- |-Simon White, Internet Services Manager, Certified Check Point CCSA. |-MTDS Internet, Security, Anti-Virus, Linux and Hosting Solutions. |-MTDS 14, rue du 16 novembre, Agdal, Rabat, Morocco. |-MTDS tel +212.3.767.4861 - fax +212.3.767.4863
"SW" == Simon White simon@mtds.com writes:
SW> Kinda tough if you don't have the mailman version in the
SW> cookie. A good reason to put it in there, from now on, if it
SW> isn't there.
SW> Any other parameter in the cookie which has changed could be
SW> detected by the new version and force an expiration of the
SW> cookie immediately so that the problem will go away.That's not really the problem. The issue is that there are Apache rewrite rules you can use to map most of your MM2.0 lists and MM2.1 lists to the same url space. That means your browser will return both cookies in the http request because it doesn't know that they're really separate urls. You don't want to expire your MM2.0 cookies since you may still have to admin that older list. You just don't want those other cookies to cause a false error in the cookie parsing code.
Try the patch; I'm pretty confident it'll work. -Barry
participants (3)
-
barry＠python.org -
Simon White -
william+mm＠hq.newdream.net