Closed Bug 999688 Opened 11 years ago Closed 11 years ago

cookie allow for session doesn't work

Categories

(Core :: Networking: Cookies, defect)

31 Branch
x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: taz, Unassigned)

Details

I have configured Firefox so it doesn't accept cookies from websites. But I have ~20 exceptions to allow specific websites to keep them during a session or until they expire. Steps to reproduce: - Disable the automatic accepting of cookies by unchecking "accept cookies" in prefs. - Allow a site to set cookies for the current session. - Close firefox (or shut down your PC) Actual results: When I start or restart Firefox, the site still has the (supposedly) per-session permission I gave it previously to set cookies. Cookies for the site are not present but if a go to website with per-session permission cookies are again present. Expected results: When I start or restart Firefox (ie. start a new session), the site no longer has permission to set cookies. Also, cookies for the site should have been deleted. I have tested with a new profil.
Component: Untriaged → Networking: Cookies
Product: Firefox → Core
This might be the expected behavior (to only clear the cookies after restart), although "Allow for session" is a little confusing.
Flags: needinfo?(josh)
Yes, I can understand the confusion over what "Accept for session" really means - permissions are always persistent, while the data they allow (such as cookies) can be scoped to the current session.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Flags: needinfo?(josh)
Resolution: --- → INVALID
Ok, but Firefox have or will have a option for stop permission when you quit your session ?
We don't support that right now, and there are ongoing discussions in bug 967812 to support this for private window sessions.
(In reply to taz from comment #3) > Ok, but Firefox have or will have a option for stop permission when you quit > your session ? Only if you accept all cookies and 'keep them until close Firefox'.
You need to log in before you can comment on or make changes to this bug.