Hello, i have the same problem : (

In middleware, you can use this.

export const config = {
matcher: ['/((?!_next|static).*)'],
};

@Asiatic Lion , @Transvaal lion

No, same problem

middleware: GET /admin/agencys/9b4244bd-963e-4675-aff7-a9e034914ff8
middleware: GET /admin/agencys/9b4244bd-963e-4675-aff7-a9e034914ff8
GET /admin/agencys/9b4244bd-963e-4675-aff7-a9e034914ff8 200 in 70ms
GET /admin/agencys/9b4244bd-963e-4675-aff7-a9e034914ff8 200 in 47ms

This is the logs

this is the middleware:

export async function middleware(request) {

console.log('middleware:', request.method, request.nextUrl.pathname);

}

export const config = {
matcher: ["/admin", "/admin/:path((?!_next|api|.\..).)", "/login", '/((?!_next|static).)'],
};

export const config = {
matcher: ['/((?!_next|static).*)'],
};

not admin

but i want to this middleware only run on admin

But stills the same

hm...

I make a middleware to refresh token, and get this problem because it refresh two times and i get a error

But then i simplify the middleware and saw that he runs 2 times only in dynamic routes i think

so strange

yes, it is

yes is the same as me

can you invite me your simple project?

Is a long project ahaha

With authentication

Ok

np

Can we call?

no

Ok np

Falas portugues?

No

import { NextResponse } from 'next/server';
import type { NextRequest } from 'next/server';

export function middleware(request: NextRequest) {
const { pathname } = request.nextUrl;

// Skip Next.js internals and data requests
if (
pathname.startsWith('/_next') ||
request.headers.get('x-nextjs-data')
) {
return NextResponse.next();
}

console.log('Middleware running for:', pathname);

// Your refresh logic here
// ...

return NextResponse.next();
}

export const config = {
matcher: ['/admin/:path*'],
};