-
Notifications
You must be signed in to change notification settings - Fork 26k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Customer headers are removed with internationalisation #21507
Comments
@Timer I noticed you removed the release milestone, is there a particular reason for this or simply workload capacity related? |
Hi @tomevans18 can you provide a minimal reproduction where you are seeing this behavior? I'm not able to reproduce this on the latest version of Next.js |
Hi @ijjk, I have given you access to a repo where this is happening. Many thanks |
This mentions how locale routes are transformed when `locale: false` is not used to explain why regex routes might not match with i18n. Closes: #21507
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
What version of Next.js are you using?
10.0.3
What version of Node.js are you using?
15.3.0
What browser are you using?
Chrome
What operating system are you using?
macOS (intel)
How are you deploying your application?
Vercel
Describe the Bug
Within the next.config.js, if you have customer headers and deploy to Vercel, these headers are added to the response.
When you then add internationalisation some of these custom headers are removed.
Observed headers being removed:
Expected Behavior
Custom headers should be populated in the response when using internationalisation.
To Reproduce
Deploy to Vercel and observe the custom headers within the response
Add internationalisation to your project
Deploy to Vercel
Observe the above noted custom headers have been removed
The text was updated successfully, but these errors were encountered: