[WIP] RFC6265bis: "Lax-Allowing-Unsafe" applies to cross-site redirect #2351
Conversation
This file contains 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.
This PR is a WIP while waiting on data to show us that this is the correct approach.
Until #1348, the spec mistakenly didn't define the same-site-ness to include the redirect chain. When some UAs, such as Chrome, attempted to apply the changes in #1348 they found that users complained of breakage. Bug reports hinted that this occurred during similar situations as Lax+POST, i.e.: young cookies with an unsafe method.
This changes modifies lax-allowing-unsafe to also include cookies that being blocked due a cross-site redirect with an unsafe method. It retains the suggested 2 min limit on cookie age.