SmooaiNextEdge: include Next.js RSC headers in HTML cache key (0.1.6)#5
Merged
Conversation
…1.6) The HTML cache policy used headerBehavior:'none', so CloudFront cached the HTML document and the React Server Component (RSC/Flight) payload for the SAME URL under the SAME key — Next.js serves both at one URL, differentiated only by the `RSC` request header. A cached RSC payload then got served for a document request: pages rendered as raw text (`1:"$Sreact.fragment"…`), never hydrated, forms were dead, sign-in "did nothing". Hit live on smoo.ai's apex cutover. Whitelist RSC / Next-Router-Prefetch / Next-Router-State-Tree / Next-Url in the HTML cache key so the document and each RSC variant get distinct entries (same set OpenNext / sst.aws.Nextjs use). Bumps @smooai/deploy -> 0.1.6. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
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.
Live bug from smoo.ai's apex cutover. The HTML cache policy used
headerBehavior:'none', so CloudFront collided the HTML document and the RSC/Flight payload (same URL, differentiated only by theRSCheader) — a cached RSC payload got served as the document, pages rendered as raw text and never hydrated (forms dead, sign-in 'did nothing'). Fix: whitelistRSC/Next-Router-Prefetch/Next-Router-State-Tree/Next-Urlin the cache key (same as OpenNext/sst.aws.Nextjs). Bumps to 0.1.6. 🤖 Generated with Claude Code