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
Hi there - my Next.js:15.3.1 site using middleware with next-intl:3.26.5 enabled and has rewrites stopped working on Netlify after upgrading from plugin-nextjs:5.10.6 to plugin-nextjs:5.10.7.
The default language for i18n is de redirecting to / (https://next-intl.dev/docs/routing).
The following Header is set: x-middleware-rewrite: /de for the request /.
If you use /enfor the English version, no redirect will be triggered as /en is a valid URL segment. In this case, the website will work as expected.
The selected language (the i18n plugin detects the browser language) will be saved in a Cookie NEXT_LOCALE=de. Disabling this behavior via localeCookie: false (https://next-intl.dev/docs/routing#locale-cookie) does not fix the issue.
It seems like the new Cookie behavior of the plugin does not work with the next-intl plugin.
Best
Marcel
The text was updated successfully, but these errors were encountered:
mschel
changed the title
[@netlify/plugin-nextjs:5.10.7] infinity loop on netlify after upgrading
[@netlify/plugin-nextjs:5.10.7] infinity loop on netlify with next-intl enabled
Apr 22, 2025
@mschel Are you still able to reproduce the issue? The reproduction I had created for this issue is now working as intended, so curious if it's also resolved on your end.
Hi there - my Next.js:15.3.1 site using middleware with next-intl:3.26.5 enabled and has rewrites stopped working on Netlify after upgrading from plugin-nextjs:5.10.6 to plugin-nextjs:5.10.7.
The default language for i18n is
de
redirecting to/
(https://next-intl.dev/docs/routing).The following Header is set:
x-middleware-rewrite: /de
for the request/
.If you use
/en
for the English version, no redirect will be triggered as/en
is a valid URL segment. In this case, the website will work as expected.The selected language (the i18n plugin detects the browser language) will be saved in a Cookie
NEXT_LOCALE=de
. Disabling this behavior vialocaleCookie: false
(https://next-intl.dev/docs/routing#locale-cookie) does not fix the issue.It seems like the new Cookie behavior of the plugin does not work with the next-intl plugin.
Best
Marcel
The text was updated successfully, but these errors were encountered: