Closed
Bug 20683
Opened 25 years ago
Closed 22 years ago
RFE: Database interface for storing/accessing cookies...
Categories
(Core :: Networking: Cookies, enhancement, P3)
Core
Networking: Cookies
Tracking
()
People
(Reporter: roland.mainz, Unassigned)
Details
(Keywords: helpwanted)
As the summary says: An interface for storing/acessing cookies in databases.
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Comment 1•25 years ago
|
||
I'm afraid I don't understand what is being requested here. If you are asking
for a user interface to access the cookies collected in your browser, then it
already exists. Go to the cookie viewer which is accessible from the menu item
edit/wallet/display-cookies.
If you are asking for a facility to access cookies in some arbitrary database
outside of the browser, then this is not something that belongs in the browser
but should be a separate stand-alone tool.
If you are asking for the ability to create (not just access) cookies, then this
is of very limited use to nearly all users. What would you do with such a
cookie?
Unless you can give concrete examples of what it is that you are asking for and
why it would be useful, I have to close this request out as invalid. If you
have such examples and justification, then feel free to include it here and
reopen the bug report.
| Reporter | ||
Updated•25 years ago
|
Status: RESOLVED → REOPENED
| Reporter | ||
Comment 2•25 years ago
|
||
My idea was to store the cookies in a name service (like LDAP etc.) that
multiple browser sessions on different hosts can share cookies and other profile
data instead of getting them from prefs.js
Updated•25 years ago
|
Resolution: INVALID → ---
Target Milestone: M20
Comment 3•25 years ago
|
||
OK, now I understand what you are asking for. Of course you meant to say
"cookies.txt" rather than "prefs.js" but I understood what you meant.
Updated•25 years ago
|
Status: REOPENED → ASSIGNED
Updated•25 years ago
|
Assignee: morse → nobody
Status: ASSIGNED → NEW
Comment 4•25 years ago
|
||
This enhancement is not going to get done unless somebody on the web volunteers
to do it.
Assigning all open "nobody@mozilla.org" bugs to "leger@netscape.com" to weed
thru.
Assignee: nobody → leger
Moving back to nobody@mozilla.org. This is where the helpwanted will be
assigned until someone picks them up.
Assignee: leger → nobody
Comment 8•24 years ago
|
||
Netscape nav triage team: based on Steve Morse's pre-triage recommendation, this
is not a beta stopper.
Keywords: nsbeta1-
Comment 9•23 years ago
|
||
I think this is a dup of bug 17048 the all known profile roaming. Both ask for
profile data stored on a centralized server.
Comment 10•22 years ago
|
||
Agreed on it being a dup. Roland, if you disagree, please reopen this.
*** This bug has been marked as a duplicate of 17048 ***
Status: NEW → RESOLVED
Closed: 25 years ago → 22 years ago
Resolution: --- → DUPLICATE
Comment 11•22 years ago
|
||
intend seems to be covered by roaming bugs, yes
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•