Catch all 404 not working if not using a next-intl function #1047
ScreamZ
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
About this section of the documentation
It's said that routes not matching the middleware filter end up in 404. That's not exactly true, consider the following example
Don't work (user land on
[locale]/page.tsx
)Works
If you don't use any next-intl function on this page, the user never get redirected. This is kind of an edge case (a big one even), but it could be nice knowing it. Maybe should it be added to the documentation ?
:)
Beta Was this translation helpful? Give feedback.
All reactions