Pages Router: gssp/getStaticProps responses missing default and user-set Cache-Control…
- User
Pages Router: gssp/getStaticProps responses missing default and user-set
Cache-ControlheaderThis 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
Pages Router gssp responses lack
Cache-Controlheaders. Tests expect the defaultprivate, no-cache, no-store, max-age=0, must-revalidatefor gssp pages and custom values set viares.setHeader('Cache-Control', ...), but vinext returnsnull. The default header is not applied and usersetHeadercalls are dropped.Expected: "private, no-cache, no-store, max-age=0, must-revalidate" Received: nullEstimated Impact
~2 test failures across the deploy suite.
Affected Test Suites
test/e2e/getserversideprops/test/index.test.ts(2 failures)
Recommendation
-
Reproduce first in vinext's own test suite. Add a Pages Router gssp page and assert the response carries the default
Cache-Controlheader; add a second page that overrides it viares.setHeaderand assert the override sticks. -
Emit the default gssp Cache-Control. When serving a gssp response in deploy mode, set
Cache-Control: private, no-cache, no-store, max-age=0, must-revalidateunless the user set it explicitly. -
Preserve
res.setHeaderoverrides. Make sure headers set during gssp dispatch are forwarded to the final HTTP response.
Interface
No new interfaces are introduced.
- Assistant
I'll trace how Pages Router gSSP responses are built and where
Cache-Controlshould be applied. - Assistant
Implementing the fix: default gSSP
Cache-Controlin the response builder, dev server, and_next/datapath. - Assistant
Adding the fixture page and tests.
- Assistant
Fixed missing
Cache-Controlheaders on Pages RoutergetServerSidePropsresponses.Root cause
gSSP responses only set
Cache-Controlfor ISR pages (isrRevalidateSeconds) or nonce-bearing pages. Plain gSSP pages skipped it entirely, and user overrides viares.setHeader('Cache-Control', ...)were dropped on the/_next/datapath because the generated entry readgsspRes.headersinstead ofgsspRes.getHeaders().Changes
-
pages-page-response.ts— After applying gSSP headers, emit the Next.js defaultNEVER_CACHE_CONTROLwhen noCache-Controlis already set. -
dev-server.ts— Same default for HTML and/_next/dataresponses in dev. -
pages-server-entry.ts— Fix/_next/dataheader forwarding to usegetHeaders(), and apply the defaultCache-Controlfor gSSP when the user did not override it. -
Tests
- Unit tests in
pages-page-response.test.ts - Integration tests in
pages-router.test.ts(dev + prod) - Fixture page
ssr-cache-control.tsxfor override behavior
- Unit tests in
Verification
pnpm test tests/pages-page-response.test.ts pnpm test tests/pages-router.test.ts -t "Cache-Control" pnpm test tests/pages-router.test.ts -t "serves pages from production build end-to-end"All passed.
-
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- fable-5Compare side by side →
- fable-5Compare side by side →