Closed
Bug 46163
Opened 25 years ago
Closed 25 years ago
Cookies via SSL don't get saved
Categories
(Core :: Networking: Cookies, defect, P3)
Tracking
()
VERIFIED
INVALID
People
(Reporter: matt, Assigned: morse)
References
()
Details
Build 2000072009, Linux 2.2.14, RedHat 6.1
I'm not sure about this, since I've only seen it on Source Forge, but
it seems like cookies that are sent/granted via SSL/HTTPS aren't saved
when the browser shuts down; I've looked in the cookies file and there
aren't any cookies from Source Forge there. To reproduce:
1) Get a Source Forge account at http://www.sourceforge.net/
2) Log in, and select the "stay with SSL" option.
3) Quit Mozilla without loging out
4) Start up Mozilla and go to Source Forge. You will no longer be logged
in.
| Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
| Assignee | ||
Comment 1•25 years ago
|
||
It would be very unusual for a site to let you stay logged in across browser
sessions -- especially an ssl site. The cookie, if there is one, is probably
set to expire at the end of the session and that would explain what you have
observed.
To verify this, use the cookie manager to view the cookies that are set after
step 2. If there is a sourceforge cookie, when is it set to expire?
Closing this out as invalid. If I'm wrong and the site really set a cookie with
more permanance, then please reopen.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
| Reporter | ||
Comment 2•25 years ago
|
||
You're right, the cookie is set to expire when the browser closes.
Marking verified.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•