59f7676966
**Note**: This PR is applying again changes landed #31935 that were reverted from an investigation. This PR fixes #30398 By default Next will polyfill some fetch APIs (Request, Response, Header and fetch) only if fetch is not found in the global scope in certain entry points. If we have a custom server which is adding a global fetch (and only fetch) at the very top then the rest of APIs will not be polyfilled. This PR adds a test on the custom server where we can add a custom polyfill for fetch with an env variable. This reproduces the issue since next-server.js will be required without having a polyfill for Response which makes it fail on requiring NextResponse. Then we remove the code that checks for subrequests to happen within the **sandbox** so that we don't need to polyfill `next-server` anymore. The we also introduce an improvement on how we handle relative requests. Since #31858 introduced a `port` and `hostname` options for the server, we can always pass absolute URLs to the Middleware so we can always use the original `nextUrl` to pass it to fetch. This brings a lot of simplification for `NextURL` since we don't have to consider relative URLs no more. ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [x] Errors have helpful link attached, see `contributing.md`
13 lines
569 B
TypeScript
13 lines
569 B
TypeScript
/**
|
|
* Given a URL as a string and a base URL it will make the URL relative
|
|
* if the parsed protocol and host is the same as the one in the base
|
|
* URL. Otherwise it returns the same URL string.
|
|
*/
|
|
export function relativizeURL(url: string | string, base: string | URL) {
|
|
const baseURL = typeof base === 'string' ? new URL(base) : base
|
|
const relative = new URL(url, base)
|
|
const origin = `${baseURL.protocol}//${baseURL.host}`
|
|
return `${relative.protocol}//${relative.host}` === origin
|
|
? relative.toString().replace(origin, '')
|
|
: relative.toString()
|
|
}
|