Replies: 2 comments 6 replies
-
It seems like your issue is caused by your custom middleware code that writes to I'll move this to a discussion since it's a usage question and not a bug report. |
Beta Was this translation helpful? Give feedback.
5 replies
-
That configuration cause an unexpected redirection too, outside the webpage export const routing = defineRouting({
// A list of all locales that are supported
locales: ["en", "es"],
// Used when no locale matches
defaultLocale: "en",
// localePrefix: "never",
localePrefix: {
mode: "as-needed",
prefixes: {
es: "/es",
en: "/",
},
},
}); I read and thought that I needed many top-level domains per region to improve the SEO, but it works fine with |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
I have a folder called protected to views like not found, maintenance, countdown, the idea is that folder can only be accessed using rewriting, I saw that the browser got that like a redirection, why? because next-intl middleware returns a 307, causing a redirection and rendering a 404 request, I can't change that response status
Verifications
Mandatory reproduction URL
https://capyschool.com/
Reproduction description
Expected behaviour
That it don't redirect to
/es/protected/countdown
middleware
requests.ts
routing.ts
layout.tsx
Beta Was this translation helpful? Give feedback.
All reactions