From 2a2e15b18a33ad12b3b71ec2f1efc0e93f65262d Mon Sep 17 00:00:00 2001 From: Satya Patel Date: Tue, 12 May 2026 22:52:53 -0700 Subject: [PATCH] chore(api): drop redundant matcher entry from CORS proxy MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The proxy.ts middleware had two matcher entries: "/((?!_next|ingest|monitoring|).*)" "/(api|trpc)(.*)" The second is fully covered by the first — Next's matcher dedupes overlapping patterns so behaviour is unchanged, it's just dead config. Dropping it leaves a single, easier-to-read pattern. No CORS or routing changes; chat-attachments stays local-only per Avi's follow-up decision, so the matcher doesn't need finer-grained scoping. --- apps/api/src/proxy.ts | 1 - 1 file changed, 1 deletion(-) diff --git a/apps/api/src/proxy.ts b/apps/api/src/proxy.ts index 6451123950c..1553b5be329 100644 --- a/apps/api/src/proxy.ts +++ b/apps/api/src/proxy.ts @@ -67,6 +67,5 @@ export default function proxy(req: NextRequest) { export const config = { matcher: [ "/((?!_next|ingest|monitoring|[^?]*\\.(?:html?|css|js(?!on)|jpe?g|webp|png|gif|svg|ttf|woff2?|ico|csv|docx?|xlsx?|zip|webmanifest)).*)", - "/(api|trpc)(.*)", ], };