`src/pages/_middleware` running for requests outside of `pages` folder

What version of Next.js are you using?

12.0.3

What version of Node.js are you using?

14.16.0

What browser are you using?

Chrome

What operating system are you using?

macOS

How are you deploying your application?

Vercel

Describe the Bug

Our project utilizes a src folder to hold our pages directory. Inside we added a _middleware.js. If I log the req object inside the middleware, it seems to be running for not only our pages, but for our assets as well.

This has had the effect of breakout out site.webmanifest failing requests on URLs inside our next.config.js rewrites array, and causing certain edge functions to time out.

This is our middleware which ignores a rewrite to `/system` and only attempts to run on req objects containing a page name. This works locally however fails when deployed to Vercel.

import { NextResponse } from "next/server";

const middleware = (req) => {
  const { page, nextUrl } = req;

  const isActualPage = !!page.name;

  const hasCookies =
    req.cookies.refresh && req.cookies.payload && req.cookies.access;

  const publicPage = /^\/(signin|signup).*$/.test(nextUrl.pathname);

  const companyOrInvestorPage = /^\/(company|investor)\/.*$/.test(
    nextUrl.pathname
  );

  const systemUrl = /^\/(system).*$/.test(nextUrl.pathname);

  if (systemUrl || !isActualPage) {
    return NextResponse.next();
  }

  if (isActualPage && !publicPage && !companyOrInvestorPage && !hasCookies) {
    return NextResponse.redirect(`/signin?redirect=${nextUrl.pathname}`);
  }

  if (isActualPage && publicPage && hasCookies) {
    return NextResponse.redirect(`/`);
  }

  return NextResponse.next();
};

export default middleware;

Expected Behavior

We expected this to only run on the request to the page, so we would not have to ignore certain path names

To Reproduce

Create a project with a rewrite, a src/pages folder with a _middleware.js inside.

[edelfrade]

Possible duplicate of #31324

[github-actions[bot]]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.