-
Notifications
You must be signed in to change notification settings - Fork 148
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
Remove consideration of same-site redirect chain #2750
Conversation
The work to re-add the requirement back into RFC6265tris is being track by issue #2751 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not an editor, but LGTM (given that it reflects reality).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huh. I guess this obviates the comment I made in the previous PR.
It surprises me we didn't implement this. I though we did. :/
If it's the case that we didn't, and that no one else did, then yeah, removing LGTM.
Yeah, we did implement this - but we had to back it out (and re-spin stable, IIRC?) because it broke too many sites. :( |
Correct, Chrome had to disable the change. Firefox had a similar experience. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, given the context.
Closes #2104
This PR removes the requirement of checking the request's redirect chain during the computation of same-site-ness.
This is being done because RFC6265bis is blocked by this work but we have yet to find a way to implement it in a web compatible way. In the interest of moving RFC6265bis forward the requirement is being removed.