Open
Bug 355048
Opened 18 years ago
Updated 3 years ago
Capability to Edit Cookie Expiration Dates
Categories
(SeaMonkey :: Preferences, enhancement)
SeaMonkey
Preferences
Tracking
(Not tracked)
NEW
People
(Reporter: david, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5 Mnenhy/0.7.4.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5 Mnenhy/0.7.4.0 The Cookie Manager should allow for changing the expiration date of a selected cookie. This should include setting an expiration date for a session-only cookie to make it persistent. Some Web sites that generally require a login will set a cookie so that the user can then re-enter the site without logging-in again. Such cookies may be either session-only or have a near-term expiration. Other sites set very long-term expirations. Users should have the ability to manage the expirations of cookies and not leave this strictly under the control of the Web sites that set them. This would align with the concept that, in Preferences, the Cookie Manager is under "Privacy & Security". This would be a definite improvement over the current user management capability to either delete a cookie or leave it as set by the originating Web site. Reproducible: Always This is NOT a duplicate of bug #87296, which requested broader editing capabilities.
Comment 1•17 years ago
|
||
this is most definitely in the realm of a cookie management extension, unless you can provide some use cases for regular users wanting this feature.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WONTFIX
Reporter | ||
Comment 2•17 years ago
|
||
A number of Web sites set cookies when you login. This is especially true of secure sites (e.g., banks). A cookie gets set when you answer an identifying question (e.g., in what city was your father born). If that cookie is found the next time you log in, the question is bypassed. This whole process is very annoying, so I would like to extend the lifetime of such cookies. Also, as I indicated in the original description, there are some sites that will completely bypass the login if a certain cookie is found. This is common with newspaper sites. Both of these uses would be helpful to the average user. In the future, I think at least a brief discussion should be held before closing such bug reports.
Status: RESOLVED → VERIFIED
Reporter | ||
Updated•17 years ago
|
Status: VERIFIED → REOPENED
Resolution: WONTFIX → ---
Comment 3•17 years ago
|
||
Since nsICookie already exposes an API for setting a cookie's expiry time, I'm assuming this request is for UI that lets end-users adjust the values. Presumably it should therefore be filed against SeaMonkey (the browser you appear to be using), not a Core component.
Assignee: nobody → prefs
Status: REOPENED → NEW
Component: Networking: Cookies → Preferences
Product: Core → Mozilla Application Suite
QA Contact: networking.cookies
Comment 4•17 years ago
|
||
(Note, also, that this feature request has been WONTFIXed for Firefox.)
Comment 5•16 years ago
|
||
(Filter "spam" on 'prefs-nobody-20080612'.)
Assignee: prefs → nobody
QA Contact: prefs
Reporter | ||
Comment 6•13 years ago
|
||
Mozilla/5.0 (Windows NT 5.1; rv:7.0) Gecko/20110923 SeaMonkey/2.4 I would still find this to be a useful capability.
You need to log in
before you can comment on or make changes to this bug.
Description
•