high85%
Segment prefetch uses wrong route segment path for links after bandwidth cap, causing 404 under rewrites
In Next.js 16.3.0, when a page contains links with different route shapes and a middleware rewrite maps some URLs to a different locale prefix, the client-side segment prefetch scheduler reuses the segment path from a previously processed link (e.g., the home route) for later links that are starved by the 4-request network cap. This results in 404 responses for the affected prefetch _rsc requests. Navigation still works due to fallback, but browser consoles are polluted with errors and E2E tests fail.