You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Verify that the Cache-Control header is not overriden
Verify that the custom header is overriden
Current vs. Expected behavior
Currently the app is configured to proxy requests to nextjs.org with the URL /rewrite.
I expect all the headers specified in the NextResponse.headers to be overriden. In particular the Cache-Control header.
Currently it is not overriden. Custom headers work.
Provide environment information
Operating System:
Platform: win32
Arch: x64
Version: Windows 11 Enterprise
Available memory (MB): 32488
Available CPU cores: 16
Binaries:
Node: 20.15.0
npm: N/A
Yarn: N/A
pnpm: N/A
Relevant Packages:
next: 14.2.13 // Latest available version is detected (14.2.13).
eslint-config-next: N/A
react: 18.3.1
react-dom: 18.3.1
typescript: N/A
Next.js Config:
output: N/A
Which area(s) are affected? (Select all that apply)
Middleware
Which stage(s) are affected? (Select all that apply)
next dev (local), next start (local)
Additional context
No response
The text was updated successfully, but these errors were encountered:
isn't this the desired behaviour? priority should be given to the website being redirected to, so that things dont break there. Also, there's no docs regarding the desired behaviour, so you may argue otherwise
Link to the code that reproduces this issue
https://github.com/Gebov/nextjs-rewrite-headers
To Reproduce
Current vs. Expected behavior
Currently the app is configured to proxy requests to nextjs.org with the URL /rewrite.
I expect all the headers specified in the NextResponse.headers to be overriden. In particular the Cache-Control header.
Currently it is not overriden. Custom headers work.
Provide environment information
Which area(s) are affected? (Select all that apply)
Middleware
Which stage(s) are affected? (Select all that apply)
next dev (local), next start (local)
Additional context
No response
The text was updated successfully, but these errors were encountered: