rsnext/test/e2e/app-dir/interception-middleware-rewrite/middleware.ts

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

14 lines
349 B
TypeScript
Raw Normal View History

interception routes: support middleware rewrites (#48450) This PR fixes an edge case when using interception routes and rewrites. The issue was that the default state of the router tree incorrectly assumed that the base pathname would be the referrer URL for the interception but it turns out the tree/what we want to intercept can be different in the case of a rewrite. The fix consists of using the same method that we use to extract the pathname from the current tree so that we can get the correct referrer pathname. ## For Contributors ### Improving Documentation or adding/fixing Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> fix #48396 link NEXT-1018
2023-04-17 10:07:31 +02:00
import { NextResponse } from 'next/server'
export default function middleware(req) {
if (!req.nextUrl.pathname.startsWith('/en')) {
return NextResponse.rewrite(new URL(`/en${req.nextUrl.pathname}`, req.url))
}
}
export const config = {
matcher: [
'/((?!api|_next/static|favicon|.well-known|auth|sitemap|robots.txt|files).*)',
],
}