[[...page]] at root and public files #71397
Unanswered
haf
asked this question in
App Router
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I want to have a catch all route, because I want to serve pages from /[[...page]], not from
/page/[[...page]].However, this conflicts with e.g.
/favicon.icoand the server returns 500 internal server error, due to this.Matchers only work with middleware, but it would be great if I can whitelist a set of files that I don't want to serve in an
export const config = { matcher: '/((?!api|_next/static|_next/image|favicon.ico).*)' };from the page.Except reorganising the page hierarchy, removing the catch-all at the root, I haven't found a good way to manage this. Any ideas on how it could be done?
Beta Was this translation helpful? Give feedback.
All reactions