Secure sign on (SSL I guess) fails after a few uses, stating that my broswer is rejecting cookies




15 years ago
14 years ago


(Reporter: charliep51, Assigned: bugzilla)


Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.8

I use e-Bay a lot.  I use the secure-sign on feature.  For many features, e-Bay
requires occasional re-verification and thus a new sign-on.  This sometimes
happens unexpectedly.  After a while, I have to exit the browser and re-load
before it accepts cookies again.

This is an extremely aggravating problem.  It _always_ happens eventually, and
e-Bay is already so aggravating that this problem is just the last straw.  As it
is, I have to go back to using the blecherous Microsoft product because I can
no longer stand this aggravation.

Reproducible: Always
Steps to Reproduce:
1. Sign on to e-Bay and bid on, say, adult auctions which require occasional
2. Wait until you are really need the browser for quick action, and notice that
Murphy requires at these times for the reverification step to be performed.
3. Observe that the browser has suddenly stopped accepting cookies so that you
can no longer sign on and then watch your favorite auction item evaporate into
someone else's "win" column.

Actual Results:  
I decided to stop using this product.

Expected Results:  
The software should continue to accept cookies even after repeated sign-ons.
Charles E. Perkins, do you see this problem in a current release/build like
firefox 1.0.2 ?
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.