See Firefox Bug #206203, my posts there. Cookie problem. Browser doesn't log in automatically.




15 years ago
14 years ago


(Reporter: rlf9, Assigned: darin.moz)



Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a2) Gecko/20040714
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a2) Gecko/20040714

Mozilla unable to retain allegedly saved login cookies from many sites where
that option exists, e.g., Compuserve, Morningstar, Comcast, Hewlett-Packard, to
name a few. 

Reproducible: Always
Steps to Reproduce:
1.Join Morningstar Premium, then log in, checking box to retain cookie.
2.Log out
3.Log in again

Actual Results:  
Login info is lost

Expected Results:  
Login info is retained

Mac OS 10.3.4, G4 Powerbook. This is a very old problem which I've been dealing
with through many builds with new profiles each time, and on several different
Macs and PCs. I've tried brand-new cookie files too, to no avail.
So how's this not a duplicate of bug 206203 ?

Comment 2

15 years ago
bug 206203 got morphed into an aviary-only bug (a recent regression). this,
apparently, is older...

reporter, please generate a cookie log for the affected sites, per, and attach it here.

Comment 3

15 years ago
1. I'm using Macs and don't know how to generate a Mac cookie log. The link
provided applies to Linux and Windows only.

2. This is no different from #206203 except that it applies to Mozilla instead
of Firefox. I thought each browser had its own list. Sorry if I've been mistaken.

Comment 4

14 years ago
Assuming this is still a problem with newer builds.
Open up Terminal(/Applications/Utilities)
if you use tcsh
setenv NSPR_LOG_MODULES cookie:4
setenv NSPR_LOG_FILE ~/cookies.log
if you use bash just use the linux directions except with diffrent paths.

Note I don't use/know Mac I got this from google.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.