Render the custom 404 page when a middleware rewrite dead-ends in an empty 404#17284
Draft
matthewp wants to merge 2 commits into
Draft
Render the custom 404 page when a middleware rewrite dead-ends in an empty 404#17284matthewp wants to merge 2 commits into
matthewp wants to merge 2 commits into
Conversation
🦋 Changeset detectedLatest commit: ec41420 The changes in this PR will be included in the next version bump. This PR includes changesets to release 395 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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
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.
Changes
404.astropage was skipped and a blank response was returned instead./404before the reroute guard could apply. Both error handlers (prod and dev) now detect this and retry the error page withskipMiddleware: true— the same fallback used when middleware throws. Rewrites that produce a real body are left untouched, so intentional error-render rewrites keep working.Testing
rewrite-app.test.tscovering the [Middleware] The 404 page is not working when using rewrite #17281 scenario (rewrite → empty 404 renders the custom 404 page), a direct-hit 404 baseline, and the documentednext()→rewrite('/')on-404 pattern.Docs