Layout Redirect During Client Navigation Causes Repeated ?_Rsc Requests And Blank Page

The App Router's client navigation incorrectly retains the redirect result from the shared layout's server component fetch. When the initial RSC request for /test receives a redirect to /test/1/1, the router follows it, but the subsequent RSC request for /test/1/1 incorrectly inherits or replays the same redirect flag/cache entry instead of rendering the target layout/page. This causes an infinite loop of fetching the target RSC payload while never committing the UI.

1. Clone https://github.com/heecheon92/nextjs-redirect-bug at commit 9b397509ac86f03e2557d916ca6482d4e1010851. 2. Run `npm ci` and `npm run dev` (Next 15.1.7). 3. Open `/` and click 'Enter the evil loop'. Observe blank page at `/test/1/1` and repeated `/test/1/1?_rsc=...` requests. 4. Directly opening `/test/1/1` succeeds. 5. Stop dev, run `npm run build && npm run start`, click link again: production also loops.

This workaround relies on Edge Middleware being available in your deployment environment. If your platform does not support middleware, or if the redirect depends on data fetched in the layout (not available in middleware), this may not apply. Ensure the matcher only targets the intended /test route to avoid unintended redirects. Test both direct and client navigations after applying. Rollback: revert middleware.ts to the previous header-only version and restore the layout redirect. Note: middleware redirect uses 307; use 308 if the redirect is permanent to avoid SEO/caching implications.