feat(build): emit a real 404 page + _redirects to end the soft-404 - #32
Merged
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
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.
Every unmatched URL (a mistyped page, a stale or nonexistent
/_api/{uid}.jsonan agent requested) was served the home page with HTTP 200, so a miss was indistinguishable from a hit. This emits a real404.htmlat the site root (the name Cloudflare Pages serves for a miss) plus a_redirectswhose sole rule/* /404.html 404applies only to paths matching no static asset and no Function - real pages and the/mcpFunction are untouched.Found by the output-audit workflow (cross-surface dimension). Whether
_redirectsalone overrides the project'snot_found_handlingis verified on the live deploy below; if the setting still wins, the assets are in place for the flip.