Delete HTTP headers Cookie2 and Set-Cookie2#13965
Merged
sideshowbarker merged 1 commit intomdn:mainfrom Mar 16, 2022
bershanskiy:http-headers-cookie2
Merged
Delete HTTP headers Cookie2 and Set-Cookie2#13965sideshowbarker merged 1 commit intomdn:mainfrom bershanskiy:http-headers-cookie2
sideshowbarker merged 1 commit intomdn:mainfrom
bershanskiy:http-headers-cookie2
Conversation
Contributor
sideshowbarker
approved these changes
Mar 16, 2022
Member
|
Yeah, these are essentially just cruft and it’s hard to imagine anybody having any need for them at all at this point |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Delete HTTP headers Cookie2 and Set-Cookie2
Motivation
These headers are obsolete and have not been used anywhere in a while now. For context, the proposed standard RFC 6265 which obsoleted them was published in April 2011.
Supporting details
See MDN tables for
Cookie2andSet-Cookie2.Chrome and Firefox do not process these headers, they just treat them as any other nonsensical "magic bytes" passing on the wire.
Related issues
mdn/browser-compat-data#15405
Metadata