i18n configuration. The pathname can contain 2 different locales and it works (f.e. /en/de/).

[vordgi]

What version of Next.js are you using?

12.0.3

What version of Node.js are you using?

14.17.5

What browser are you using?

Chrome

What operating system are you using?

Windows

How are you deploying your application?

next start

Describe the Bug

When I use i18n configuration I can see page in 3 difference urls.

For example, if I have page /cards/ - it will be available at:

1. /cards/ (that's ok, we expect it)
2. /en/cards/ (that's ok too)
3. /en/de/cards/ (what?)

(In the last case language will be /de/)

Expected Behavior

The page should be available only at:

1. /cards/ (that's ok, we expect it)
2. /en/cards/ (that's ok too)
   Not at /en/de/cards/. On this page I am expecting a 404 error

To Reproduce

Enable i18n in some project.

Here a good example with this error: https://github.com/vercel/next.js/tree/canary/examples/i18n-routing

The main page will be available at , /en, /en/nl;

gsp - at /gsp, /en/gsp, /en/fr/gsp;

etc

[vordgi]

https://github.com/vordgi/next.js/tree/bugfix/second-locale-in-pathname (#31229)

If I understand correctly what going on - the path has been replaced in 2 places:

• at next-server.ts - https://github.com/vordgi/next.js/blob/canary/packages/next/server/next-server.ts#L1299
• at router.ts - https://github.com/vordgi/next.js/blob/canary/packages/next/server/router.ts#L166

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.