proxy.ts does not execute in production when behind Cloudflare Proxy (middleware.ts works)

Link to the code that reproduces this issue

https://github.com/shivaluma/report-bug-next16-proxy https://github.com/shivaluma/report-bug-next16-proxy/tree/middleware

To Reproduce

To Reproduce

1. Create a new Next.js project (or use any existing Next.js 16.0.3 project):

npx create-next-app@latest

2. At the project root, create a file named middleware.ts:

// middleware.ts
import { NextResponse } from "next/server";
import type { NextRequest } from "next/server";

export function middleware(req: NextRequest) {
  console.log("MIDDLEWARE RUNNING:", req.nextUrl.pathname);
  return NextResponse.next();
}

export const config = {
  matcher: ["/(.*)"],
};

3. Deploy the project behind Cloudflare Proxy enabled (Cloudflare orange-cloud ON → proxied traffic).

4. Visit any route (e.g., /). You will see the expected log output: MIDDLEWARE RUNNING: /

5. Now rename the file from middleware.ts → proxy.ts, and update the function name:

// proxy.ts
import { NextResponse } from "next/server";
import type { NextRequest } from "next/server";

export function proxy(req: NextRequest) {
  console.log("PROXY RUNNING:", req.nextUrl.pathname);
  return NextResponse.next();
}

export const config = {
  matcher: ["/(.*)"],
};

6. Remove the old middleware.ts file. Ensure only proxy.ts exists in the project root.

7. Redeploy behind Cloudflare Proxy enabled.

8. Visit any route again.

---

Actual Result

• No logs appear.
• The proxy.ts file does not execute at all.
• Requests behave as if no middleware/proxy file exists.

Expected Result

proxy.ts should execute exactly like middleware.ts, with identical config and behavior, including when Cloudflare Proxy is turned on.

Configuration Usage: output: "standalone"

Current vs. Expected behavior

Current Behavior

• When using middleware.ts, the middleware executes correctly in:

  • local developm