Old description:
> [https://code.djangoproject.com/ticket/31933 #31933]
>
> `SESSION_COOKIE_SAMESITE` is documented (in Django 3.1) with the options
> 'Strict', 'Lax', 'None' and False. However, False means cookies will be
> sent without `SameSite`, which means some browsers (Chrome, Dolphin) will
> give it default such as 'Lax', which is different than what used to be in
> the past. I think this default should be documented in all active
> versions of Django. Maybe it's also better to add that using False is not
> recommended.
New description:
[https://code.djangoproject.com/ticket/31933 #31933]
`SESSION_COOKIE_SAMESITE` is documented (in Django 3.1) with the options
'Strict', 'Lax', 'None' and False. However, False means cookies will be
sent without `SameSite`, which means some browsers (Chrome, Dolphin) will
give it default such as 'Lax', which is different than what used to be in
the past. I think this default should be documented in all active versions
of Django. Maybe it's also better to add that using False is not
recommended.
Also, document that with Chrome, if you use 'None' the cookie must be
secure.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/31934#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* cc: אורי (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/31934#comment:3>