RSC caching redirect behavior fix via Vary header #79363
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
…t-Encoding" value when response type is RSC to prevent CDN caching
|
|
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
|
This should be it. Please fix this soon. |
|
Also having this issue. Please bring this fix sooner |
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.
Fixes #79346
When RSC response is received by the browser for a page, the CDN can cache it and the payload is shown to the user as-is if they close and re-open the tab. This behavior is fixed by adding a
Varyheader to the response and setting it to the valueRSC, Next-Router-State-Tree, Next-Url, Accept-Encodingso that the response is not cached by the CDN when the user closes and opens the tab again.Demo:
fix.rsc.behaviour.mov