Is there a way to exclude specific path from running on middleware?

Answered

Nile Crocodile posted this in #help-forum

Nile CrocodileOP

2024-09-12T14:48:11.793Z

Is there a way to exclude specific path like "/about/" or "careers" from running middleware.

This is code i am using right now but it seems, this will exclude all paths starting with "about".
So it will exclude "about-test" also, which is something i don't want?

export const config = {
matcher: [
"/((?!about|careers|contact-us|api|_next/static|_next/image|favicon.ico|robots.txt|manifest.json|browserconfig.xml).*)",
],
};

Answered by iyxan23

hi, this is a workaround i had just figured out, looks kinda clunky but it works 😄

View full answer

15 Replies

@Nile Crocodile Is there a way to exclude specific path like "/about/" or "careers" from running middleware. This is code i am using right now but it seems, this will exclude all paths starting with "about". So it will exclude "about-test" also, which is something i don't want? export const config = { matcher: [ "/((?!about|careers|contact-us|api|_next/static|_next/image|favicon.ico|robots.txt|manifest.json|browserconfig.xml).*)", ], };

iyxan23

2024-09-12T14:52:42.018Z

hi, this is a workaround i had just figured out, looks kinda clunky but it works 😄

Answer

Asian black bear

2024-09-12T14:52:59.637Z

If you don't want to mess with the matcher just check for the path in the middleware and early return using next() in there

gin

2024-09-12T14:57:04.618Z

u can do this

export const config = {
  matcher: [
    "/((?!^/about/$|^/careers$|^/contact-us$|^/api|^/_next/static|^/_next/image|^/favicon.ico|^/robots.txt|^/manifest.json|^/browserconfig.xml).*)",
  ],
};

iyxan23

2024-09-12T14:57:56.516Z

i honestly think it would be more intuitive if the next team, instead of using a single regex, used glob matching on a list instead. imagine doing { exclude: ["/careers/*", "/about/*"] }, that'd be pretty awesome :)

@iyxan23 i honestly think it would be more intuitive if the next team, instead of using a single regex, used glob matching on a list instead. imagine doing `{ exclude: ["/careers/*", "/about/*"] }`, that'd be pretty awesome :)

Nile CrocodileOP

2024-09-12T15:00:47.314Z

I am upvoting for that. 🙂

@iyxan23 hi, this is a workaround i had just figured out, looks kinda clunky but it works 😄

Nile CrocodileOP

2024-09-12T15:02:34.209Z

iyxan23

2024-09-12T15:04:20.207Z

seems like you're missing a backslash \ on the w there

but huh that's odd, even if it was a regular w, it should've been able to be parsed

might want to try gin's regex to see if that works

Jboncz

2024-09-12T15:05:16.381Z

    let requestedPath = request.nextUrl.pathname;

    //No authentication needed for route
    if (mw_IsNoAuthRoute(requestedPath) == true) {
        return NextResponse.next();
    }

To @Asian black bear point, this is how I do it.

@gin u can do this typescript export const config = { matcher: [ "/((?!^/about/$|^/careers$|^/contact-us$|^/api|^/_next/static|^/_next/image|^/favicon.ico|^/robots.txt|^/manifest.json|^/browserconfig.xml).*)", ], };

Nile CrocodileOP

2024-09-12T15:15:18.591Z

Tried, it does not work.

@Asian black bear If you don't want to mess with the matcher just check for the path in the middleware and early return using `next()` in there

Nile CrocodileOP

2024-09-12T15:32:31.694Z

This would still be logged as invocation of middleware. Right? I can still see that path being logged for triggering middleware even when using something like:

if (request.nextUrl.pathname === "/about/") {
    return NextResponse.next();
  }

Asian black bear

2024-09-12T15:33:09.002Z

Yes, but it really doesn't matter.

Nile CrocodileOP

2024-09-12T15:33:23.729Z

yeah, just wanted to to check

@Asian black bear Idea is i guess that it would just not run any function but go further to that path.