overwrite redirect SSG meta.status to 200 for RSC requests #80379
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.
For a static route that simply returns a
redirect
:the SSG generates a
.meta
file for the route at build time, that looks like:On
next start
, if a request matches this route, the status code is retrieved from the file and returned to the response. This is perfectly fine for DOC requests. However, if the request is an RSC request, its RSC payload should have already encoded the redirect instruction:Specifically,
Hence, it would be fine to simply return 200 status code.
There are two motivations for this change:
meta.status = 307
)Existing E2E tests should cover this change.