Session cookie is not removed after closing the tab and exiting the browser
Categories
(Firefox :: Session Restore, defect, P3)
Tracking
()
People
(Reporter: egil, Unassigned)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(1 file)
(deleted),
text/html
|
Details |
Reporter | ||
Comment 1•6 years ago
|
||
Reporter | ||
Comment 2•6 years ago
|
||
Reporter | ||
Comment 4•6 years ago
|
||
Reporter | ||
Comment 5•6 years ago
|
||
Reporter | ||
Comment 6•6 years ago
|
||
From the linked issue (https://bugzilla.mozilla.org/show_bug.cgi?id=443354#c29):
At the very least can we get rid of the sessions saved for sites with no open tabs?
We already do that. If that's not what you see, please file a new bug.
As far as I can tell, Firefox has stopped "doing that", this is the "new bug", and it hasn't been updated in 3 years.
It's a security issue. Many sites tell you "close this tab then quit the browser" to ensure that you're logged out, which seems like reasonable advice, but Firefox doesn't actually do the thing that the user-agent is supposed to do -- the thing that the above quote says it does.
Dale, can we please get a higher priority / security-relevant flag on this, so it actually gets some attention from the team?
As I commented on bug 530594 , I was able to isolate the issue to Firefox 55, to a change made between the Nightly builds of 2017-04-07 and 08. (So, please also flag the issue as a regression, because this used to work correctly.)
Comment 10•4 years ago
|
||
Hey Johann, do you think this needs security triage / flags?
Comment 11•4 years ago
|
||
(In reply to James B from comment #9)
As I commented on bug 530594 , I was able to isolate the issue to Firefox 55, to a change made between the Nightly builds of 2017-04-07 and 08. (So, please also flag the issue as a regression, because this used to work correctly.)
Thanks, James. The regression range is a big help!
Here is the changelog between Nightly builds 2017-04-07 and 2017-04-08:
In this changelog, bug 912717 ("Don't let SessionCookie collection jank the chrome process") looks like it me related.
Comment 12•4 years ago
|
||
I'm reading down from the top of that bug and almost immediately I see suggestions like "recursively walking history entries is expensive, we should cache it"... it's like being in the audience at the beginning of a horror film -- don't go in there, cache invalidation is One Of The Hard Problems!
At the end, they link to bug 1354523, which has had no activity for 4 years. "We should write some tests, I'll get to it Soon". Man, I've said that sentence a few too many times. Anyway, I voted for it, and I'll leave a comment over there pointing back to here.
Updated•4 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Description
•