Rewrites failing after deployment

[PepijnSenders]

What version of Next.js are you using?

10.0.5

What version of Node.js are you using?

15

What browser are you using?

Chrome

What operating system are you using?

macOS

How are you deploying your application?

K8S

Describe the Bug

Each time after deploying we have a small blip of rewrites failing. It looks like next.js is redirecting users to the rewritten URL which then causes a 404.

Expected Behavior

For users never to be redirected to the rewritten URL's.

To Reproduce

I'm not sure how to reproduce this yet, working on that case. But our rewrites look something like:

{
  source: "/plans",
  destination: "/legacy/funnel-fragment/plans"
}

ELB logs of people going to the pages that yield a 404 (/legacy/funnel-fragment/plans) and all other pages that have a rewrite enabled. As you can see it started happening on Jan 21, which is when we upgraded from [email protected] to [email protected].

[PepijnSenders]

I feel like this PR might be fixing it: #21410, but need to test it still.

[PepijnSenders]

Reverting back to 10.0.3 fixed this issue. Would be great to look at this though because we wanted to use the optimizations to next/image!

[PepijnSenders]

As you can see it doesn't happen anymore since reverting back to 10.0.3. For a test I blocked the _next/data URL's and it recovers perfectly with this version. With 10.0.5 it forgets the rewrites.

[ijjk]

Hi, can you narrow in on a more specific version or provide additional details as this is hard to investigate without a reproduction and such a wide version bump since lots of changes are made between v10.0.3 and v10.0.5

[PepijnSenders]

@ijjk You mean testing if it also happens in 10.0.4? I could also check if it has perhaps been fixed in latest already.

[ijjk]

If you could narrow it down to a specific canary that would help the most as it would narrow down the changes a lot, also checking the latest version would definitely be good 👍

[PepijnSenders]

Seems like it works again in the last canary. I guess I'll leave it up to you guys why 10.0.5 is broken, might be smart to deprecate that version because for us it was quite critical as you can see in the graphs.

[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.