Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-fetch scheme navigation params initiator origin isn't always set correctly #9517

Closed
domfarolino opened this issue Jul 13, 2023 · 0 comments · Fixed by #9532
Closed

Non-fetch scheme navigation params initiator origin isn't always set correctly #9517

domfarolino opened this issue Jul 13, 2023 · 0 comments · Fixed by #9532
Assignees

Comments

@domfarolino
Copy link
Member

domfarolino commented Jul 13, 2023

Non-fetch scheme navigation params's initiator origin is populated in two places:

The second instance above is setting the initiator origin to something completely bogus — the "origin" concept, not even a variable. I think this should instead be responseOrigin, to be the last fetch-scheme origin in the redirect chain, but need to take a closer look.

@domfarolino domfarolino self-assigned this Jul 13, 2023
domenic pushed a commit that referenced this issue Jul 19, 2023
Fixes #9517.

Also adds a note explaining the relationship between responseOrigin, response's URL, and response's location URL.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

1 participant