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
Is your feature request related to a problem? Please describe.
I have another middleware that performs a rewrite to /app when the request host is app.myhost.com. This rewrite is colliding with the rewrite that next-intl performs.
Given that NextJS only allows 1 middleware rewrite in the request lifecycle. Isn't it too much for the library to consume that single intent?
Is there a way to solve this without using a rewrite within next-intl?
Is there a way to solve this without needing to change anything in next-intl?
Describe the solution you'd like
Add a way to opt out from the rewrite and do a redirect instead
Describe alternatives you've considered
Been trying to solve this issue by parsing and massaging the response that the next-intl middleware returns with no success.
The text was updated successfully, but these errors were encountered:
There was a similar request recently here, maybe this helps: #573. Generally, the middleware is composable, allowing e.g. rewrites on top before processing a request.
Is your feature request related to a problem? Please describe.
I have another middleware that performs a rewrite to
/app
when the request host isapp.myhost.com
. This rewrite is colliding with the rewrite thatnext-intl
performs.Given that NextJS only allows 1 middleware rewrite in the request lifecycle. Isn't it too much for the library to consume that single intent?
Is there a way to solve this without using a rewrite within next-intl?
Is there a way to solve this without needing to change anything in next-intl?
Describe the solution you'd like
Add a way to opt out from the rewrite and do a redirect instead
Describe alternatives you've considered
Been trying to solve this issue by parsing and massaging the response that the next-intl middleware returns with no success.
The text was updated successfully, but these errors were encountered: