Springr
Proxy Route Match
All tools

Proxy Route Match

Test Next.js proxy.ts matcher patterns against your site URLs and see which routes get intercepted.

Matcher config

JSON array or one path pattern per line. Matches proxy.ts config.matcher.

Test URLs

One path or full URL per line. Matching runs on pathname only, like Next.js proxy.

Match results

5 intercepted4 skipped
InputPathnameProxyMatched by
//Skipped/((?!api|_next/static|_next/image|favicon.ico|.*\..*|_next).*)
/dashboard/dashboardSkipped/((?!api|_next/static|_next/image|favicon.ico|.*\..*|_next).*)
/dashboard/settings/dashboard/settingsSkipped/((?!api|_next/static|_next/image|favicon.ico|.*\..*|_next).*)
/api/users/api/usersIntercepted—
/_next/static/chunks/main.js/_next/static/chunks/main.jsIntercepted—
/_next/image?url=%2Flogo.png&w=64&q=75/_next/imageIntercepted—
/favicon.ico/favicon.icoIntercepted—
/styles.css/styles.cssIntercepted—
/blog/my-post/blog/my-postSkipped/((?!api|_next/static|_next/image|favicon.ico|.*\..*|_next).*)

About Proxy Route Match

Test Next.js proxy.ts matcher patterns against your own URLs and see which routes get intercepted. Avoid running proxy logic on static files and API routes by mistake.

How to use it

  1. Enter your matcher patterns.
  2. Add the site URLs and paths you want to test.
  3. See which routes get intercepted and adjust the pattern until only the right ones match.

Frequently asked questions

What is a proxy matcher in Next.js?
A matcher is the pattern set in the config of Next.js proxy.ts (previously middleware) that decides which request paths run your proxy code.
Why does my proxy run on unexpected routes?
Most often the pattern is too broad and also catches static files, _next assets or API routes. Testing it here against real URLs shows exactly what gets intercepted.