#31218: response.set_cookie method not accepting "samesite" key set to "None" in
release versions
--------------------------------------------+-----------------------------
Reporter: bolinocroustibat | Owner: nobody
Type: Uncategorized | Status: new
Component: HTTP handling | Version: 2.2
Severity: Normal | Keywords: set_cookie,
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
--------------------------------------------+-----------------------------
Google is now requesting, starting from Chrome 80 (from February 4th), to
add "SameSite=None; Secure" to cookies (https://www.chromium.org/updates
/same-site), otherwise it will not be considered as not CSRF-proof anymore
by Chrome.
In all Django release branches, response.set_cookie method is not
accepting "samesite" key set to "None" , but it seems it has been done in
master branch (https://www.chromium.org/updates/same-site).
Do you know when it will be merged to release branche(s)?
--
Ticket URL: <https://code.djangoproject.com/ticket/31218>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/059.de4c05fe156bdec96bb6bc7505733386%40djangoproject.com.
