Preserve documentation entry queries during the site cutover - #9
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.
Requests such as
/doc?view=1bypassed the exact Cloudflare route, and the Worker's/documentation/redirect target is unavailable while Jekyll remains live. Use trailing-wildcard routes so queries reach the Worker, with an explicit namespace guard that passes ordinary production website pages through unchanged. Redirect the documentation entry point to/documentation.html, which works during the classic-site soak and through Astro's fallback afterward.Add smoke checks for queried robots rules and the actual landing page. Unknown staging paths return 404 without fetching back into the custom-domain Worker. Validation: 21 Worker tests and both environment dry runs pass; final CI and staging verification required before production redeployment. The indexing policy and immutable R2 content are unchanged.