Conversation
apurvagoenka-method
approved these changes
Apr 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Note
Low Risk
Low risk: a small, targeted change to redirect-host comparison logic; behavior only changes for redirects that differ by port/userinfo but share the same hostname.
Overview
Fixes cross-domain redirect detection in both headless and standard request flows by comparing
Hostname()instead ofHostwhen deciding whether to block redirects.This prevents same-host redirects that only change port (or other
Hostcomponents) from being incorrectly flagged as cross-domain whenIgnoreCrossDomainRedirectsis enabled.Written by Cursor Bugbot for commit 157ea79. This will update automatically on new commits. Configure here.