Apply SameSite=Lax exception only on safe methods - #3335
Conversation
be441b5 to
07198b7
Compare
f368d1f to
5f8972d
Compare
karlseguin
left a comment
There was a problem hiding this comment.
Any thoughts on https://re-sync.nl/en/blog/samesite-lax-cookie-bypass/ ?
(With the official documentation about it: https://www.chromium.org/updates/same-site/faq/#q-what-is-the-lax-post-mitigation)
Interesting find & article... Turns out there's also a section that touch this in RFC6265bis: 5.6.7.2. "Lax-Allowing-Unsafe" enforcement As discussed in Section 8.8.6, compatibility concerns may necessitate "Lax-allowing-unsafe" is not a distinct value of the SameSite |
3fb2614 to
cee0296
Compare
|
This currently conflicts w/ #3448; since both touch |
cee0296 to
58193cc
Compare
Specifically to distinguish cross-site iframe navigation from top-level navigation, this PR reworks how `SameSite=Lax` moved. Since we're not checking if its a navigation alone now, the field for it is also renamed to `lax_allowed`.
58193cc to
380bdcf
Compare
|
This now also includes a solution for what #3448 trying to fix. |
|
LGTM, but I think this is worth tests in ../demo/ (or as an html test in this project if that works). There's 1 unit test for the Cookie.Jar, but the feature requires all the layers to do their part, which isn't tested anywhere. |
|
Agreed, will add this through |
On top of #3293.