fix(prerenderer): write responses with json signature to original path #1963
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.
π Linked issue
β Type of change
π Description
See #1962 and nuxt/nuxt#24487 for some context
When prerendering, a route without
.html
extension (like/foo
or/foo.json
, etc) could contain a JSON response (wrongly because returned by h3 handler or a SSR renderer).Nitro were trusting purely on content-type to detect HTML routes and write
/foo
topublic/foo/index.html
.With this PR, if response contents of
/foo
contains a JSON signature, we write it topublic/foo
as-is.π Checklist