[Internationalization] Redirect with `{ locale: false }` and dynamic isn't working properly.

[raulfdm]

Bug report

Describe the bug

Redirect with { locale: false } isn't working properly.

Context

Before describe the bug, I need to give you some context about what problem I'm trying to solve.

I recently switch my website default locale from pt to en. It means that some old URLs I had localized, now would be inverted, for example:

URL example:

Before: /blog/e-o-coronavirus-hein (default lang PT)
After: /pt/blog/e-o-coronavirus-hein (Default lang EN)

The problem

What's is happening now is I can't just setup this redirect via next.config.js or via vercel.json (but I'll focus on next config).

The way I would try to solve that is setting up something like this:

module.exports = {
  async redirects() {
    return [
      {
        source: "/blog/e-o-coronavirus-hein",
        destination: "/pt/blog/e-o-coronavirus-hein",
        permanent: true,
      },
    ];
  },
};

This won't work and that's comprehensible. I assume when I try to access /blog/e-o-coronavirus-hein, since my browser is in English, it'll try to resolve the request locale to /en. But the stranger thing is that the redirect works but it concatenates everything and I'm being redirected to: /en/pt/blog/e-o-coronavirus-hein.

That's weird but makes sense because I'm embedding the locale in the path.

In the docs it says we can turn off the locale process, that should do the job, right?

module.exports = {
  async redirects() {
    return [
      {
        source: "/blog/e-o-coronavirus-hein",
        destination: "/pt/blog/e-o-coronavirus-hein",
        locale: false,
        permanent: true,
      },
    ];
  },
};

But now if I try to access /blog/e-o-coronavirus-hein, instead being redirected to /pt/blog/e-o-coronavirus-hein, I just reach 404.

I assume that somehow it's thinking that's is a valid route (because I use pages/blog/[slug].js) and it does not consider the redirect setup.

Another problem (which I can open another issue if you want to) is when I try to redirect from a url which even does not exist from an existing one:

module.exports = {
  async redirects() {
    return [
      {
        source: "/2018/08/09/coronavirus",
        destination: "/pt/blog/e-o-coronavirus-hein",
        locale: false,
        permanent: true,
      },
    ];
  },
};

In this case I also get 404.

To Reproduce

I prepare a demo site with some deeper explanation how to test this problem but:

1. Access: https://next-redirect-bug.vercel.app/
2. Check the Defective redirects section
3. Click in both links which should redirect

Expected behavior

As a dev user, I want to be able to setup a redirect from a /blog/some-post to /<locale>/blog/some-post .

Screenshots

Not applicable

System information

• OS: Pop!_OS
• Browser (if applies) [e.g. chrome, safari]: any
• Version of Next.js: [e.g. 10.0.1]: 10.0.3-canary.3
• Version of Node.js: [e.g. 12.0.0]: 12.19.1
• Deployment: [e.g. next start, next export, Vercel, other platform]: Vercel

Additional context

• Repository: https://github.com/raulfdm/next-redirect-bug
• Related: redirects i18n locale:false not working as expected #19302
• Ensure i18n custom routes resolves correctly  #19766

Update

• This also does not work with rewrites

[raulfdm]

Any help in this case?

[raulfdm]

Update

I upgrade the demo project to next@10.0.4-canary.2 and it seems not fixed yet. I'm not sure if it's an edge case.

#19766

[ramiyahya]

@raulfdm I was having a similar issue. Just out of interest, do you have a routes entry in your now.json or vercel.json file? If so, try removing it and see if it works. I had a few routes doing some rewrites etc. in my now.json file. Removing it fixes the issue for me.

Note - I had to refactor some of my pages to use Next's dynamic routing instead of doing rewrites using legacy routes approach. See https://vercel.com/docs/configuration#project/routes for more info.

[raulfdm]

Hey @ramiyahya , thanks for answering. No man, I don't have routes configured.

Where do you put your redirects? In you vercel.json or inside next.config.js? I tried both places already and it seems I have the same result ;/

[IanMitchell]

I'm also running into this - exact same behavior as described. Going to spend some time poking around the codebase tomorrow, hoping the fix isn't too hard 🤞

[raulfdm]

I'm also running into this - exact same behavior as described. Going to spend some time poking around the codebase tomorrow, hoping the fix isn't too hard crossed_fingers

Hey @IanMitchell ... thanks for sharing.

I've been checking every canary release but it seems nobody fix this problem yet.

I'm not sure if it's that complex or it has low prio or even if my PR is clear enough so if you can review that, the examples it would be great.

[robertcoopercode]

I think this might also affect rewrites in addition to redirects since I'm having a similar issue: #21096