App Router: RSC navigations drop `?_rsc=` query param on redirect/rewrite
#1,529 opened on May 22, 2026
Repository metrics
- Stars
- (8,563 stars)
- PR merge metrics
- (Avg merge 1d 1h) (462 merged PRs in 30d)
Description
This issue was created by an agent analysing CI failures from the Next.js Deploy Suite (vinext
mainvs Next.jsv16.2.6, 2026-05-22).
Problem
Tests intercept RSC fetches that follow a server-driven redirect or rewrite and expect the new request URL to still carry the _rsc query param. vinext does not preserve _rsc on the redirected/rewritten URL, so the intercepted URL does not match the matcher.
toContain('_rsc') matcher received null/undefined URL
Estimated Impact
~2 test failures across the deploy suite.
Affected Test Suites
test/e2e/app-dir/rsc-query-routing/rsc-query-routing.test.ts(2 failures)
Recommendation
-
Reproduce first in vinext's own test suite. Add a test that performs an RSC navigation that hits a redirect/rewrite and asserts the follow-up request URL still carries
_rsc. -
Preserve
_rscacross redirect/rewrite. When the server returns a redirect/rewrite in response to an RSC request, the new request URL should retain the_rscquery param so it is treated as an RSC fetch.
Part of #1328.