[Django] #31933: Regression in Set-Cookie which affects Django users

[Django]

#31933: Regression in Set-Cookie which affects Django users
----------------------------------------+------------------------
Reporter: אורי | Owner: nobody
Type: Bug | Status: new
Component: Core (Other) | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
----------------------------------------+------------------------
It seems that there is a regression in `Set-Cookie` in browsers such as
Chrome and Dolphin, which affects Django users. `SESSION_COOKIE_SAMESITE =
None` does not work any more with those browsers. This affects all
versions of Django, and especially where it's not possible to explicitly
set cookies to `SameSite=None` (Django <= 3.0).

You can read about it in the following links:

- [https://www.chromestatus.com/feature/5088147346030592 Cookies default
to SameSite=Lax]
- [https://www.chromestatus.com/feature/5633521622188032 Reject insecure
SameSite=None cookies]

You can see more information in the
[https://stackoverflow.com/q/63538073/1412564 question] I just asked on
Stack Overflow.

I think it should be made possible to explicitly set cookies to
`SameSite=None`, also in settings such as `SESSION_COOKIE_SAMESITE`, and
backport it to all working versions of Django.

--
Ticket URL: <https://code.djangoproject.com/ticket/31933>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#31933: Regression in Set-Cookie which affects Django users

-------------------------------+--------------------------------------
Reporter: אורי | Owner: nobody
Type: Bug | Status: closed
Component: HTTP handling | Version: master
Severity: Normal | Resolution: wontfix

Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0

-------------------------------+--------------------------------------
Changes (by felixxm):

* status: new => closed
* resolution: => wontfix
* component: Core (Other) => HTTP handling

Comment:

We decided that it's a new feature that will not be backported to Django
3.0, see #30862, and discussion in
[https://github.com/django/django/pull/11894 PR].

--
Ticket URL: <https://code.djangoproject.com/ticket/31933#comment:1>