This repository was archived by the owner on Nov 20, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 191
Add support for SameSite cookie property #710
Comments
This has come up before (though I can't find the issue). We were going to wait for the RFC to finish. |
Yea I couldn't find it either, I thought I had logged it before. I figured better safe than sorry. |
This sounds like something that should be added to the CookiePolicy middleware. |
Not so sure, after all we can set HTTP_Only and Secure on individual cookies, via CookieOptions. I feel it ought to go in there, along with the ability to override everything in the CookiePolicy middleware. |
Yes, I meant in addition to implementing it here. |
Ah :) |
Backlogging until spec is more stable. Ping me if you think otherwise. |
@blowdart has requested a re-triage |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
https://tools.ietf.org/html/draft-west-first-party-cookies-07
Basically add a new property SameSite with values of None, Lax and Strict.
The value should then be appended to cookies when the cookie is sent;
The text was updated successfully, but these errors were encountered: