Add support for route has field

[ijjk]

A new custom routes field has should be added to match against header, cookie, and query values. Currently only paths are allowed to matched against, adding the has field allows for more specific custom routes matching. The following shape will be used:

{
  source: '/:path*',
  has: [
    {
      type: 'header' | 'cookie' | 'query',
      key: 'some-key-to-match',
      value: 'an optionanl value to match'
    }
  ],
  destination: '/another/:path*'
}

Both the source and all has fields must be matched for the custom route to be applied.

[balazsorban44]

I wonder if the Next.js team has any specific usecases in mind for this!? 💡

[timneutkens]

I wonder if the Next.js team has any specific usecases in mind for this!? 💡

This is mostly driven by complex enterprise needs where they might have to route certain requests based on a cookie existing or a header being set from an external system. In general you don't need it in a basic Next.js application.

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.