Fix client filter case with redirects (#46317)
Follow-up to https://github.com/vercel/next.js/pull/46283 this ensures we properly handle redirects with matchers at the base and we don't use the normalized redirects when generating the filter as the breaks with i18n. x-ref: [slack thread](https://vercel.slack.com/archives/C040J1CGLHH/p1677028542232619) ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md)
Showing
Please
register
or
sign in
to comment