Attach the forensics production route - #71
Merged
Conversation
A route rather than a custom domain, matching sites/www. The DNS record that follows is a proxied placeholder pointing at RFC 5737 TEST-NET-1, so if the Worker is ever detached the hostname fails rather than serving whatever is at that address. The apex uses a real Netlify address because the apex has a rollback origin; this property has none. Deployed before the DNS record exists, deliberately. A proxied record with no route attached serves an error, and robots.txt is `Allow: /` -- whatever a crawler sees in that window is what it caches. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J53xszP5CdZLXfhRJWsSyv
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.
The route half of the cutover. Deployed before the DNS record exists, deliberately: a proxied record with no route attached serves an error, and
robots.txtisAllow: /, so whatever a crawler sees in that window is what it caches.A route rather than a custom domain, matching
sites/www. The DNS record that follows points at RFC 5737 TEST-NET-1 (192.0.2.1), so if the Worker is ever detached the hostname fails rather than serving whatever happens to be at that address. The apex points at a real Netlify address because the apex has a rollback origin; this property has none.DNS record follows immediately after this deploys.
🤖 Generated with Claude Code
https://claude.ai/code/session_01J53xszP5CdZLXfhRJWsSyv