3 people 6d07c00dee fix: allow some recursion for middleware subrequests (#60615) ...

This alters the behavior of the subrequest check to allow for 5
recursive calls to match Vercel production, ref [Slack
thread](https://pinglabsworkspace.slack.com/archives/C052S77L05C/p1694729495655489).

> [!NOTE]
> Currently limited by fetches having to forward the subrequest header
for each request which isn't ideal. Need some assistant on how to access
the request in the module context fetch override.
> No forwarding: 
![CleanShot 2024-02-05 at 22 52
10@2x](https://github.com/vercel/next.js/assets/51714798/8ae79f00-f987-4919-946c-d8363d540cef)
> With forwarding: 
![CleanShot 2024-02-05 at 22 51
31@2x](https://github.com/vercel/next.js/assets/51714798/32bd4072-9373-4cb0-ab05-f862a818e0d7)

---------

Co-authored-by: JJ Kasper <[email protected]>

2024-02-06 18:00:29 +00:00

..

app

fix: allow some recursion for middleware subrequests (#60615)

2024-02-06 18:00:29 +00:00

app-routes-subrequests.test.ts

fix: allow some recursion for middleware subrequests (#60615)

2024-02-06 18:00:29 +00:00

next.config.js

fix: allow some recursion for middleware subrequests (#60615)

2024-02-06 18:00:29 +00:00