allow explicit SameSite=None cookies#1282
Conversation
3f1600f to
fb2c36a
Compare
Codecov Report
@@ Coverage Diff @@
## master #1282 +/- ##
==========================================
- Coverage 80.47% 80.46% -0.02%
==========================================
Files 159 159
Lines 18541 18540 -1
==========================================
- Hits 14921 14918 -3
- Misses 3620 3622 +2
Continue to review full report at Codecov.
|
|
Could you add entry to changes.md |
fb2c36a to
59509d5
Compare
|
IMHO this should not be considered a breaking change, but a bug fix. Anyone using |
59509d5 to
464db0c
Compare
|
this is breaking change even if original behavior is wrong. we have to mention change in default behavior in migration.md |
|
the migration.md file mentions the change now |
Codecov Report
@@ Coverage Diff @@
## master #1282 +/- ##
==========================================
- Coverage 80.47% 80.46% -0.02%
==========================================
Files 159 159
Lines 18541 18540 -1
==========================================
- Hits 14921 14918 -3
- Misses 3620 3622 +2
Continue to review full report at Codecov.
|
|
There are more browsers than just chrome & there should be a way to have no samesite (existing behaviour) or a samesite with a value of |
|
@cetra3 omitting the call to set samesite will result in no samesite flag being sent in the set-cookie header eg. most of the tests dont set it and pass without it being asserted the issue is that |
|
Ah right, I don't have an issue with it if that is the case (I.e, if it's not set there is no change in behaviour) |
dfc2ba8 to
315dbf1
Compare
929c214 to
8182fa0
Compare
|
Thanks! |
fixes actix#1035 (cherry picked from commit a328794)
Given the upcoming changes in Chrome to default SameSite-less cookies to Lax, we should allow the option to explicity set None cookies.
This could be considered non-breaking while Chrome's changes are still in beta.
It's also possible this change should be packported to 0.x and 1.x branches.
fixes #1035