Fix absolute redirect detection #9689
Merged
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Ran into issues with our
URL
creation fix with Remix integration tests using atest://test.com
base, so re-thought the approach a bit. We were sort of conflating 2 things - whether a redirect was external and whether it was absolute. In both cases we want to skip the relative redirect logic, but we do not need to check for external on the server since the browser will handle redirecting to the external domain. Instead, we can do a simplerisAbsolute
check in shared code (noURL
creation required) and limit ourisExternal
check to client side code where we can more reliably create URLs withwindow.location.origin
Follow up to #9682
Closes remix-run/remix#4740