Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Middleware does not match when using basePath and default locale #2472

Open
serhalp opened this issue Jun 13, 2024 · 0 comments
Open

Middleware does not match when using basePath and default locale #2472

serhalp opened this issue Jun 13, 2024 · 0 comments
Labels
Next.js e2e test failure Errors identified through the Next.js repo e2e tests Next.js

Comments

@serhalp
Copy link
Contributor

serhalp commented Jun 13, 2024

A pages router site with both basepath and i18n enabled does not match middleware targeted at the root unless a locale is in the URL. It should match when using the default locale

Demo:

Data

The following is parsed automatically by the Next.js repo e2e test report generator.

test: test/e2e/middleware-matcher/index.test.ts
reason: Middleware does not match when using basePath and default locale

@serhalp serhalp added type: bug code to address defects in shipped code Next.js e2e test failure Errors identified through the Next.js repo e2e tests labels Jun 13, 2024
@serhalp serhalp added the Next.js label Jun 14, 2024 — with Linear
@serhalp serhalp removed the type: bug code to address defects in shipped code label Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Next.js e2e test failure Errors identified through the Next.js repo e2e tests Next.js
Projects
None yet
Development

No branches or pull requests

1 participant