I'm not using 2000 but Vista/FF3 is working
You broke it?
Report to Forum Feedback.
Using windows 2000 with FF3.
Using windows 2000 with FF3.
I found that I had to "Accept third party cookies" in FF Options > Privacy.
Is yours the same?
If so, sometimes member profiles have problems, and have to be looked at by the engineers. If you wish, we can ask Lee to have a look at your profile for you, or you could post in the Forum Feedback, and just for good measure, alert on your own post, asking Lee to have a look.
I hope that helps.
Just got notice for upgrade to 3.07 version and there was a fix for a "cookie monster" bug.
Oh, this is open source material.
so, the "mysterious cookie loss" bug that we've been chasing for a while has
been nailed down - ispiked has furnished me with several 300MB+ cookie logs,
taken over the course of several days. they show that session cookies, set once
at the beginning of the browser session, are eventually evicted when the
overall cookie limit (1000) is hit. this takes several days of heavy browsing
to happen, which made it tricky to reproduce and log.
cookie eviction used to be done by lastaccessed timestamp, which is updated
every time nsCookieService::GetCookie*() is called, i.e. every time stored
cookies are sent back to the webserver. when we switched to mozstorage (bug
230933), doing this would have incurred a large perf penalty for GetCookie*(),
since it requires updating the database each time for a frequently called
method. thus we switched to a simpler solution, creation time eviction. i
didn't think this would be an issue in practice, since cookies are typically
reset by the server (to extend expiry time, update data, etc) every now and
then, which would update the creation time. thus, sites you visit often would
keep these cookies fresh. it turns out this was wrong, and certain cookies are
set just once, so after you turn over 1000 cookies they'll be gone.
the fix here will be to move back to lastaccessed eviction, and to find a way
to do this without a large perf hit. i have some ideas and numbers which i'll
This bug report is sadly somewhat vague, but was prompted by talk of similar
problems in m.d.a.firefox.
I keep losing my cookies for some sites. Facebook, Google, and Barclays Bank's
"remember account number" cookie are three examples. It doesn't seem to happen
on other sites.
I'm not sure when it started; it could well have been when I switched from
Firefox 2 to the Firefox 3 betas.
It's hard to give steps to reproduce, because it only happens occasionally -
perhaps one instance a week. I don't have enough data to know if it happens for
each site independently, or all of them at the same time. If I see it again, I
...have it right yet. I've had the CNET cookie disappear several times and never had two bank cookies do so, nor my Ebay cookies, or others. I suspect it's not just a FF3 problem but also something to do with the CNET cookie, how it's written. Another possible complication is my AVG (antivirus) keeps warning on cookies.sqlite which FF3 uses and that's supposed to be there, so I tell it to Ignore each time. Using win2000 fully updated with SP4 and Rollup1 and antivirus AVG version 8.0.237
Current version FF# is 3.07, the problem I know was while using version 3.05 I had to sign in CNET today again, but it was after the FF3 update, so don't know if that caused it.
I wonder if you might want to post this, or a link to it, in the Forum Feedback forum. Others have had similar problems and this might just be a solution they need.
Also, if we use that to alert Lee so he can let the techs know, they might want to look at their own cookie management and see if any changes are needed.
This one tip will help you sleep better tonight
A few seconds are all you need to get a better night's rest.