feat: redirect the Cloudflare Pages domain to www.uplb.tools - #17
Conversation
uplbtools.me is served by the uplbtools-me Cloudflare Pages project, not Vercel, so the vercel.json host redirect never fires there. Pages honors the _redirects file; this sends every request to the new canonical origin with the path preserved.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
| @@ -0,0 +1 @@ | |||
| /* https://www.uplb.tools/:splat 301 | |||
There was a problem hiding this comment.
This rule is unconditional on host, but the same Cloudflare Pages project (uplbtools-me) also serves PR preview deployments per .github/workflows/deploy-cloudflare.yml (pages deploy dist --project-name=uplbtools-me --branch=pr-${{ github.event.pull_request.number }}). Cloudflare Pages _redirects rules apply to every hostname tied to the project, including pr-N.uplbtools-me.pages.dev, so every preview deploy will now 301 straight to www.uplb.tools before rendering, making PR previews on Cloudflare unviewable.
|
One finding worth a follow-up (left inline): the blanket |
1 participant
uplbtools.me turns out to be served by Cloudflare Pages (deploy-cloudflare.yml), not the Vercel project, so #16's vercel.json redirect never fires on it. Pages honors public/_redirects: every request 301s to https://www.uplb.tools with the path preserved. The vercel.json rule stays as a guard in case the domain ever moves onto Vercel.