Closed dixakman closed 6 months ago
Closing, since no reproduction was provided.
As you've also pointed out, your matcher likely has an issue—this is controlled in your user code and not by next-intl
. This might be relevant for you: https://next-intl-docs.vercel.app/docs/routing/middleware#matcher-config
Description
Error "page not found" in the middleware when accessing the API
Code middleware: ` export default async function middleware(request: NextRequest) {
} `
Show "OK", but the error is "Page not found"
blocks the api, but allows a separate path Config middleware: ` export const config = { matcher: [ // Enable a redirect to a matching locale at the root '/',
}; `
Verifications
Mandatory reproduction URL
https://github.com/amannn/next-intl-bug-repro-app-router
Reproduction description
Steps to reproduce:
Expected behaviour
show response from api