85cc454023
A middleware can work as a proxy intercepting requests and then performing a `fetch` to the destination adding headers to the request / response as a "man in the middle". When using `fetch` from a middleware we are not in the context of a browser so we can't really use relative URLs, they must be always absolute. Now consider the previous case when middleware is running in *server mode*. Typically in order to know the host where we are fetching we can use the `request.nextUrl` which is given to the middleware but in this case the invoker (which is next-server) has no context of the hostname, nor the port. To solve this use case we must make the invoker of the middleware aware of the origin hostname and port. This PR: - Introduces `hostname` and `port` as options for `NextServer`. - Refactors types in `NextServer` and `NextDevServer` moving type only imports to the top of the file. - Refactors `startServer` to do a best guess on the `hostname` and `port`, passing them down. - Exposes `.port` and `.hostname` to be retrieved from the `app`. In an upcoming PR we will pass the host guess to the middleware to solve the relative URL issue. |
||
|---|---|---|
| .. | ||
| squoosh | ||
| find-page-file.ts | ||
| recursive-readdir-sync.ts | ||
| start-server.ts | ||
| utils.ts | ||