Drop the hyphenated-apex redirects, now owned by cibc-website - #36
Merged
Conversation
These four rules sent citizen-infra.org and www.citizen-infra.org here, and this file said why: the citizeninfra.org apex was a GoDaddy parking page, the wiki was the only real CIBC content on the web, and GoDaddy's own forwarding is HTTP-only so it mostly never fired. It also said to move them once the landing page shipped. It shipped, so they moved — to cibc-website/netlify.toml, repointed at citizeninfra.org and with :splat added, since the destination is now this domain's mirror rather than an unrelated site where a forwarded path would 404. The Netlify aliases moved with them, which is the part worth keeping in mind: a redirect only fires on the site that receives the request, and a hostname can be claimed by one Netlify site at a time. Rules were deployed on the destination first, then the aliases released here and claimed there, so the unclaimed window was the swap alone. Verified after the move: citizen-infra.org and www.citizen-infra.org 301 to the apex with paths preserved, wiki.citizen-infra.org still 301s here, and wiki.citizeninfra.org still serves 200. wiki.citizen-infra.org is untouched — that host is the wiki's own and stays.
✅ Deploy Preview for citizen-infra ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
Config only, no content changes.
This file carried four rules sending
citizen-infra.organdwww.citizen-infra.orgto the wiki, along with the reason and an instruction:It shipped on 2026-08-04.
citizeninfra.orgnow serves the CIBC landing page instead of a GoDaddy parking page, so the stopgap is over and the rules have moved tocibc-website/netlify.toml, repointed at the apex and with:splatadded — the destination is now this domain's mirror, so a forwarded path reaches the matching page rather than 404ing on the wiki.wiki.citizen-infra.orgis untouched. That host is the wiki's own hyphenated address and its two rules stay here.The part worth carrying forward
A Netlify redirect only fires on the site that receives the request, and a hostname can be claimed by one Netlify site at a time. So the rules and the domain aliases have to move together — moving either alone takes the domain dark, and the two cannot overlap. Sequence used:
cibc-websitefirst, where they sit inert until traffic arrivescitizen-infra.org+www.citizen-infra.orgfrom this site's aliasescitizeninfraThat keeps the unclaimed window to the alias swap alone rather than spanning two deploys.
Verified after the move
The deep link matters specifically:
/privacy/my-communityis the URL published in My Community's Chrome Web Store listing, and a redirect that dropped the path would land a reviewer on the homepage.Nothing here affects the build, the sidebar, or any page.