-
Notifications
You must be signed in to change notification settings - Fork 139
fix: join multiple Cookie header values with '; ' instead of ',' (#521) #536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
brianquinlan
merged 1 commit into
dart-lang:master
from
Yusufihsangorgel:fix/cookie-header-join
Jul 20, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Per https://datatracker.ietf.org/doc/html/rfc6265#section-4.1.1 must literal semicolons in
cookie-valuebe replaced with %3BIs that escaping done at another level?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes — that escaping (when it happens at all) is done by whoever writes the cookie, not at this layer. RFC 6265 doesn't actually mandate
%3Bor any specific escape: thecookie-octetgrammar in §4.1.1 excludes;entirely, and its guidance for servers that want to store such data is that they "SHOULD encode that data, for example, using Base64" atSet-Cookietime. The user agent sends the encoded form back untouched, so in a conforming request;only ever appears between cookie-pairs (cookie-string = cookie-pair *( ";" SP cookie-pair ), section 4.2.1), which is what keeps the RFC 9113 section 8.2.3 recombination this PR performs unambiguous. shelf keeps treating the values as opaque strings and adds or removes no encoding, same as before this change. A raw;inside a value would already be indistinguishable from a pair boundary within a single Cookie line, so the join doesn't create a new case.