Skip to content

fix(staging): preserve noindex on the root redirect - #414

Merged
juliankoehn merged 1 commit into
mainfrom
codex/docs-root-noindex
Oct 10, 2026
Merged

juliankoehn merged 1 commit into
mainfrom
codex/docs-root-noindex

Conversation

@juliankoehn

Copy link
Copy Markdown
Member

The staging image starts successfully, but the delivery smoke test fails because GET / returns a 307 without X-Robots-Tag. The initial connection-reset log is handled by the startup retry; the failing command is the final noindex assertion.

Next.js 16.0.10 config redirects discard the collected custom response headers. Move only the root redirect into the existing Fumadocs proxy, preserving its 307, destination and query string. Set staging noindex directly on proxy responses, including locale redirects. Retain the global header rule for pages/assets/API paths and the container-only standalone setting. Existing SEO config redirects are unchanged.

Validation: reproduced missing root header on the previous image; typecheck and Biome pass. The final staging Docker build and exact CI health/noindex commands pass. Root and locale redirects carry noindex, query parameters are preserved, /platform and /api/health return 200 with noindex, and following the root redirect reaches 200. Test container removed.

@juliankoehn
juliankoehn merged commit 267cec0 into main Oct 10, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant