[Cache] Document s-maxage interaction with stale-while-revalidate#30790
Open
ngayerie wants to merge 1 commit into
Open
[Cache] Document s-maxage interaction with stale-while-revalidate#30790ngayerie wants to merge 1 commit into
ngayerie wants to merge 1 commit into
Conversation
Adds documentation explaining that s-maxage disables stale-while-revalidate per RFC 9111 (s-maxage implies proxy-revalidate semantics). Updates: - cache-control.mdx: Added caution note under s-maxage definition and in SWR example - revalidation.mdx: Added caution note in Controlling stale behavior section Workaround documented: Use max-age + stale-while-revalidate at origin, then set Edge Cache TTL via Cache Rules for different edge/browser TTLs. Addresses CACHE-13507 and prevents escalations like ESCALATION-1255
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
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.
Adds documentation explaining that s-maxage disables stale-while-revalidate per RFC 9111 (s-maxage implies proxy-revalidate semantics).
Updates:
Workaround documented: Use max-age + stale-while-revalidate at origin, then set Edge Cache TTL via Cache Rules for different edge/browser TTLs.
Addresses CACHE-13507 and prevents escalations like ESCALATION-1255