Update EXPIRES info with clock skew #37745
Open
Conversation
This file contains 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
Firefox and Chromium adjust the EXPIRES value with the computed clock-skew as calculated using the response's DATE header.
ericlaw1979
requested review from
hamishwillee
and removed request for
a team
github-actions
bot
added
Content:HTTP
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.
Firefox and Chromium adjust the EXPIRES value with the computed clock-skew as calculated using the response's DATE header.
Description
Updates the info for the EXPIRES header to note that while EXPIRES is computed against the client clock, the initial value is adjusted based on the server's date.
Motivation
The clock-skew adjustment in Chrome and Firefox doesn't appear to be documented anywhere and it comes as a surprise to web devleopers.
Additional details
Related issues and pull requests