Pages router data requests returning 404 when middleware is used

[serhalp]

On sites that use pages router and have middleware, loading a page using next/link will attempt to load a JSON file, which will return a 404. If there is no middleware then it works fine. This applies even if the middleware does nothing.

Data

The following is parsed automatically by the Next.js repo e2e test report generator.

test: test/e2e/middleware-base-path/test/index.test.ts
reason: Pages router data requests returning 404 when middleware is used
test case: "Middleware base tests router.query must exist when Link clicked page routing"