44aeb083cc
When performing a redirect() with an absolute path, action-handler attempts to detect whether the resource is hosted by NextJS. If we believe it is, we then attempt to stream it. Previously we were not accounting for basePath which caused absolute redirects to resources on the same host, but not underneath the basePath, to be resolved by NextJS. Since the resource is outside the basePath we resolve a 404 page which returns back as `text/x-component` and is thus streamed back to the client within the original POST request. This PR adds a check for the presence of the basePath within absolute redirect URLs. This fixes the above problem. fixes #64413 fixes #64557 --------- Signed-off-by: Chris Frank <chris@cfrank.org> Co-authored-by: JJ Kasper <jj@jjsweb.site> |
||
|---|---|---|
| .. | ||
| browsers | ||
| next-modes | ||
| test-data-service | ||
| amp-readme.md | ||
| amp-test-utils.js | ||
| amp-validator-wasm.js | ||
| create-next-install.js | ||
| development-sandbox.ts | ||
| e2e-utils.ts | ||
| next-test-utils.ts | ||
| next-webdriver.ts | ||
| react-channel-require-hook.js | ||
| test-log.ts | ||
| turbo.ts | ||
| use-temp-dir.ts | ||