269515 - The system automatically logs me off right after I sign in, indicating a problem with the cookie.

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[darkblacksky]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Firefox/1.0

When I log onto citizensbank.com, a cookie is set that tells the site how long I
am on, and after I believe 30 minutes, the cookie expires and I am automatically
logged off.  Something is happening to this cookie in Firefox, because as soon
as I log on, I am automatically logged off.  This did not happen to me on other
similar websites, such as for my credit cards.

Just to check that there was not a problem with the website, I accessed the site
using Explorer and it opened and remained open with no problem whatsoever.

Reproducible: Always
Steps to Reproduce:
1. log onto the website
2. info is already auto-entered via the password saving function of the browser-
hit {enter} to submit.
3.

Actual Results:  
I get logged onto my account and then immediately logged off, receiving this
message:   Error #1004 - You were automatically logged off, please login again.

Expected Results:  
Allowed me to remain logged onto my account until either I logged out or my
session expired, which would automatically log me out.

Comment 1

[Jesse Ruderman]

Forgetting a cookie could be a bug, but it's not a security hole.  Making public.

Comment 2

[Daniel Veditz [:dveditz] (OOO: back Aug 26)]

possible dupe of bug 263057. flip the browser.chrome.favicons pref to false and
see if the problem goes away (no UI for it, use about:config)

Comment 3

[darkblacksky]

This if from me, the original submitter of the bug.

It appears I have been able to resolve the issue.  I am now able to log onto the
website and remain logged onto it.

When I downloaded Firefox, it automatically imported the cookies from Explorer.
 I had gone through and deleted a number of garbage cookies, leaving the ones
from frequently used sites, including the one which caused the problem.  

This cookie problem only affected the one particular website- all others
functioned just fine.

I decided to try an experiment.  I deleted the problematic cookie and then
re-accessed the website, and I was able to log on and remain logged on.  

It seemed that for this website, for whatever reason Firefox did not like the
Explorer cookie. I'm not sure how or why.  But now that a new cookie has been
set, the problem has gone away.

Comment 4

[Josh Birnbaum]

*** Bug 289388 has been marked as a duplicate of this bug. ***

Comment 5

[Jean-Marc Desperrier]

reporter, thanks to your investigation, we see where the problem comes from, but
there's not enough information yet to do anything about it, and people without a
login in citizensbankonline can not get that info.

I think comparing what the line containing your cooky in cookies.txt looks like
in the correct and in the bad case might give useful info for the resolution.
See http://kb.mozillazine.org/Firefox_:_FAQs_:_Cookies for info about cookies.txt
So it would be good if you compare the old and the new value of the cooky to see
what is different exactly. You could include in a comment the result of that
comparison, but beware of not making public any confidential data of the cooky.

In order to get the old invalid value, you can try to create a new firefox
profile, and import all your IE data inside it, using File/Import. If it
reproduces the problem, then you have the bad value in the cooky.txt of that
profile, that you can compare to the correct one in the cooky.txt of the default
profile.

Comment 6

[Gervase Markham [:gerv]]

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:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 7

[Gervase Markham [:gerv]]

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.