Closed Bug 301540 Opened 19 years ago Closed 19 years ago

"ask before accepting" only non-session cookies (silently accept session)

Categories

(Firefox :: General, enhancement)

x86
Windows XP
enhancement
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: hauser, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 It doesn't appear that firefox v1.04. really implements what has been asked for in Bug 64336. I can silently accept all cookies and limit their lifetime. But some cookies are designed with a lifetime more than just for a session for a good reason and I would rather not interfere with those (selected) applications. So, what is probably needed is a fourth option for "Keep Cookies", namely "ask me every time unless they last only for the current session" I am opening a new bug because I can neither re-open the above nor Bug 205793. Reproducible: Always
Its a hidden preference that we're not going to expose UI for. Just set network.cookie.alwaysAcceptSessionCookies to true in about:config with "ask every time set" and you're set.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
*** Bug 328549 has been marked as a duplicate of this bug. ***
Here's what I said in the duplicate bug (yes, I did extensive searching before adding it, but for some reason didn't find this one): --- The current cookie management preferences don't allow me to work in my preferred way: 1) Any session cookie should be silently allowed. These do not intrude on my privacy, so there is no reason to deny them. 2) Other (persistent) cookies should ask me, so I can decide between allowing them for this session or until they expire (or in rare cases to deny them entirely). This seems like such a straightforward and sane setting that I'm surprised it hasn't already been suggested (let alone implemented). --- Perhaps you could share the reasoning for not exposing this feature in the UI?
You need to log in before you can comment on or make changes to this bug.