Remove nameless cookies (put them behind pref)
Categories
(Core :: Networking: Cookies, task, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox152 | --- | fixed |
People
(Reporter: valentin, Assigned: valentin)
Details
(Whiteboard: [necko-triaged][necko-priority-next])
Attachments
(3 external files)
Nameless cookies have been a significant issue recently.
They are an odd edge case. Cookies like "abc" are parsed as {name: "", value: "abc" } by Firefox and Chrome. While Safari parses them as {name: "abc", value: "" }
The idea was that Firefox would mirror the nameless cookie back to the server in the same format (without an equal sign), and the server would handle it according to it's parser - as a nameless cookie, or as a valueless cookie.
However, if we have multiple nameless cookies, that entire plan breaks down. "abc; def" will result in two cookies being sent from Safari, but only one in Firefox and Chrome (as the second cookie overwrites the first one).
Also see bug 1964767 comment 3:
? From Squarcina's "Cookie Crumbles" https://www.usenix.org/system/files/usenixsecurity23-squarcina.pdf#page=10, from page 10, there's a table about analyzing nameless cookies in top 100K websites. From that analysis, nameless cookies are very rare and seem like a configuration mistake almost always (TOP 4: nameless cookies with the values HttpOnly, (empty string), Secure and =).
I think we should get rid of nameless cookies. I plan to put it behind a pref.
| Assignee | ||
Comment 1•7 months ago
|
||
Updated•6 months ago
|
| Assignee | ||
Comment 2•6 months ago
|
||
| Assignee | ||
Comment 3•6 months ago
|
||
Comment 5•6 months ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/6552c1275521
https://hg.mozilla.org/mozilla-central/rev/9b08fb675c7e
https://hg.mozilla.org/mozilla-central/rev/01a837103137
Updated•5 months ago
|
Description
•