#30862: Explicitly set `secure` for SameSite: None cookies.
-------------------------------------+-------------------------------------
Reporter: Osaetin Daniel | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: 2.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
cookies,request,response |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* component: contrib.sessions => HTTP handling
* stage: Unreviewed => Accepted
Comment:
Hi.
The link you've given implies that if `samesite` is `None` then we
**must** set `secure` —
[https://github.com/django/django/blob/5d9cf79baf07fc4aed7ad1b06990532a65378155/django/http/response.py#L198-L201
we're not doing that] so we should add an extra clause in there.
> Chrome has issued a warning that samesite has to be explicitly set to
None else the cookies won't be sent for cross-origin requests.
Is this the same point? (It reads differently to me at first glance.)
--
Ticket URL: <https://code.djangoproject.com/ticket/30862#comment:1>
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/067.4ebb2e0f7d4b79425f3dd09d118c5ef2%40djangoproject.com.
