First-party operational work
Repairing a Cloudflare Worker canonical-URL redirect loop
A production site stopped serving pages because asset requests for .html files bounced back to their clean canonical paths.
Scope
A production issue in Demonic Binary's own Next.js static export and Cloudflare Worker deployment.
Testing and validation
- Built the Next.js static export and ran the existing automated tests.
- Exercised /, /services, /contact, /robots.txt, /sitemap.xml and an unknown path against a local Worker.
- Checked successful pages returned HTTP 200 without loops, unknown paths returned HTTP 404, and the www hostname redirected to the apex.
- Repeated those checks against the public hostname following deployment.
About this example
A first-party account of the incident and the tests used to verify the fix.
