Quash An Important Mozilla Bug!
This is bad user agent behavior.
I suggest that you go sign up for a Bugzilla account if you don’t have one and then go vote on this bug.
This bug staying around will confuse new users of Firefox and annoy power users alike. The spec reads “at least”, which should mean “unlimited” except in cases where a browser developer feels that keeping a limited amount of cookies is a Good Thing™. I can’t see where it’s ever a good thing, really, to drop old cookies. Some just don’t get used very often. That’s life. Cookies are being used like keys all over the Web, and Gecko is letting you only have the 300 most recent keys that you’ve used. If #301 was really important, well, it sucks to be you.

I voted – at least if there was a limit the default behavior should have been to push out the cookie with the most dust on it. I bet I have a few that don’t look as tasty anymore that I wouldn’t mind the browser cleaning out for me.
April 22nd, 2004 at 18:52Weblogs Can Be Useful
Indeed, sometimes, advocacy gets a problem solved.
Burning Edge reports that the really offensive bug is now fixed. Bugzilla confirms that 213963 is fixed.
Spiffy.
April 26th, 2004 at 11:16Doh!
THAT’s why I kept getting blocked from logging into my website. I dumped the cache and the cookies and magically it worked. I just thought it was a dumb coincidence, since I had to reboot afterwards anyhow.
Stupid browser.
April 26th, 2004 at 11:55Squish Goes the Bug
Jason reports that the Mozilla/Firefox/$foo cookie bug has gone away in the 1.0 Preview Release … sorta.
There’s an important note about that fix, though: without doing a few manual config changes, you’ll only see a marginal improvement. The old M…
September 14th, 2004 at 16:38