Commas in etag break browser caching #3752
Merged
Conversation
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
Member
|
This was fixed by #3359 for master. Probably should've been backported to 2.3.x. |
benmccann
added a commit
that referenced
this pull request
Jan 28, 2015
Commas in etag break browser caching
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The Etag value used by the
Cachedclass include an unquoted date string containing a comma. This is parsed by the browser as a list of headers, so Chrome sends the first token of the string for If-None-Match. For example, chrome requests "If-None-Match:Sun" for the header: "ETag:Sun, 20 Dec 2015 20:11:43 GMT".