Always revalidate cached website responses - #277
Merged
Conversation
MattIPv4
force-pushed
the
MattIPv4/cache-revalidate-website-responses
branch
from
August 29, 2026 16:08
afcefaf to
e05d067
比较
MattIPv4
force-pushed
the
MattIPv4/cache-revalidate-website-responses
branch
from
August 29, 2026 16:09
e05d067 to
7e16fe0
比较
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
注册 for free
to join this conversation on GitHub.
Already have an account?
登录 to comment
1 participant
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.
Type of Change
What issue does this relate to?
N/A
What should this PR do?
Updates the cache headers for website responses to ensure that while the browser is able to cache the responses, it always revalidates the response before doing so.
What are the acceptance criteria?
Browser responses continue to work and contain the updated cache headers.