Landing page footer doc links cause ERR_TOO_MANY_REDIRECTS on aoagents.dev

[dushyant-hada-90]

Description

The four documentation links in the landing page footer (under the "Docs" heading) trigger an infinite redirect loop when clicked:

• Overview → /docs
• Architecture → /docs/architecture
• Plugins → /docs/plugins
• Changelog → /docs/changelog

Clicking any of them leads to:

This page isn't working

aoagents.dev redirected you too many times.
ERR_TOO_MANY_REDIRECTS

Steps to Reproduce

1. Go to https://aoagents.dev
2. Scroll down to the footer
3. Click any of the four links under "Docs" (Overview, Architecture, Plugins, Changelog)

Expected Behavior

Links navigate to the corresponding documentation pages without redirecting.

Actual Behavior

Browser hits a redirect loop and shows ERR_TOO_MANY_REDIRECTS.

Environment

• URL: https://aoagents.dev
• Browser: Chrome (reproducible across browsers — clearing cookies does not resolve it)

Notes

• The footer component is frontend/src/landing/components/LandingFooter.tsx
• The docs content files exist (content/docs/index.mdx, content/docs/architecture.mdx, content/docs/plugins/index.mdx, content/docs/changelog.mdx)
• The catch-all route app/docs/[[...slug]]/page.tsx handles these paths
• No redirect rules found in next.config.mjs, middleware, or hosting config (vercel.json/netlify.toml do not exist)
• The "Product" column links (/docs/installation, /docs/cli) in the same footer may also be affected

[i-trytoohard]

Triage — confirmed real, root cause is deployment-layer (not repo code)

Triaging on behalf of @dushyant-hada-90 (reported via Discord).

Verdict: Confirmed bug. Live repro below. The fix is almost certainly in the hosting/CDN config, not in this repo's application code — so this needs someone with access to the aoagents.dev deployment, not a normal repo PR.

Live evidence

Every /docs* URL returns an HTTP 307 that redirects to itself → infinite loop:

URL	Status	Location
/docs	307	/docs (self)
/docs/architecture	307	/docs/architecture (self)
/docs/plugins	307	/docs/plugins (self)
/docs/changelog	307	/docs/changelog (self)
/docs/installation	307	/docs/installation (self)
/docs/cli	307	/docs/cli (self)

Control cases: / → 200, /install → 404. So only /docs* loops; the rest of the site routes normally.

Why this is not a code bug

The docs app lives at frontend/src/landing/ (Fumadocs + Next.js). I traced the full redirect surface:

• app/docs/[[...slug]]/page.tsx — no redirect() call; calls notFound() on missing pages (would 404, not loop).
• app/docs/layout.tsx — no redirects.
• next.config.mjs — trivial: createMDX()({}). No trailingSlash, no i18n, no redirects().
• No middleware.ts anywhere in the landing app.
• No vercel.json / _redirects / _headers in the repo.

A 307 self-redirect scoped exclusively to /docs* with zero redirect logic in the codebase is the signature of a misconfigured redirect/forwarding rule at the CDN/hosting layer (aoagents.dev is fronted by Cloudflare). The repo cannot fix this — whoever controls the deployment needs to check the Cloudflare Redirect Rules / Page Rules (or wherever the edge config lives) for a pattern matching /docs*.

Minor: footer targets that don't have a page

Even after the redirect loop is fixed, several footer links point to pages that don't exist in content/docs/:

• /docs (Overview) — no root index.mdx
• /docs/changelog — no changelog.mdx
• /docs/cli — no cli.mdx

These would 404 (via notFound()), not loop. Worth resolving as a follow-up once the redirect is unblocked.

Notes on the report

• Reporter's cited paths (app/docs/[[...slug]]/page.tsx, content/docs/*) exist — they omit the landing/ prefix. Actual paths are frontend/src/landing/app/docs/[[...slug]]/page.tsx and frontend/src/landing/content/docs/.
• No assignee, no comments, no related open PRs as of now.

---

cc @codebanditssss @illegalcall @Priyanchew — this needs deploy/CDN access to fix. Flagging since the website is mid-redesign (per the website-freeze policy). Is /docs* routing going to be replaced by the redesign, or should the edge redirect rule be fixed now?

[illegalcall]

Yes it should be fixed first.
@codebanditssss can you help @dushyant-hada-90 my communicating with @AgentWrapper on this?

[somewherelostt]

Thanks for contributing to Agent Orchestrator.

This issue is being picked up by the current external contributor on-call pair:

• @neversettle17-101
• @somewherelostt

If someone is already working on this, please continue as usual.
The on-call pair is added for visibility, tracking, and support, not to take over the work.
If you need help with review, direction, reproduction, or next steps, please tag @neversettle17-101 and @somewherelostt here.

For faster context or live questions, you can also join the AO Discord.

Join the session here:
https://discord.gg/H6ZDcUXmq

Come by if you want to see what is being built, ask questions, or just hang around with the community.

[AgentWrapper]

Deployment/update status from this verification pass:

• GitHub Pages is now enabled for this repo with build_type=workflow and cname=aoagents.dev.
• The landing/docs deploy workflow succeeded on main at e783a441791419f71a0932135a760ef195e89a89: https://github.com/AgentWrapper/agent-orchestrator/actions/runs/29809559558
• PR fix(landing): emit docs routes with trailing slashes #2876 changed the static export to emit docs routes as directory indexes (/docs/index.html, /docs/architecture/index.html, etc.) and updated the landing/footer links to canonical trailing-slash docs URLs.

Verification:

• Direct GitHub Pages origin check with Host: aoagents.dev returns 200 for:
  • /docs/ -> <title>Introduction
  • /docs/architecture/ -> <title>Architecture
  • /docs/plugins/ -> <title>Plugin catalog
  • /docs/changelog/ -> <title>Changelog
• The public https://aoagents.dev path still reproduces the redirect loop through Cloudflare. Examples after the successful Pages deploy:
  • https://aoagents.dev/docs/ returns 307 Location: /docs
  • https://aoagents.dev/docs then returns 307 Location: /docs
  • nested docs paths behave the same way.

Current diagnosis: the repo/GitHub Pages artifact is correct, but public DNS is still Cloudflare-proxied (104.21.78.22, 172.67.215.24) and Cloudflare is serving/intercepting the old docs redirect behavior before traffic reaches GitHub Pages. Direct GitHub Pages HTTPS for aoagents.dev also does not have a matching certificate yet, so the remaining production step is outside this repo: update/disable the Cloudflare proxy or origin so aoagents.dev reaches GitHub Pages, then allow GitHub Pages to provision the custom-domain certificate and enable HTTPS enforcement.

Reopening because the public URL still reproduces even though the repo-side deploy fix is merged.