[Django] #32101: Handle SameSite=None Known Incompatible Clients
Django
--------------------------------------------+------------------------
Reporter: Dulmandakh | Owner: nobody
Type: Bug | Status: new
Component: contrib.sessions | Version: 3.1
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 |
--------------------------------------------+------------------------
I recently bumped into issues with SameSite=None cookies, and found that
some browsers are incompatible (https://www.chromium.org/updates/same-site
/incompatible-clients).
I think that Django should handle this, because handling this is non-
trivial. For me, I wrote custom SessionMiddleware to work around the
issue.
I would like to work on a fix, if core devs are interested and maybe
release in a next bug fix release.
--
Ticket URL: <https://code.djangoproject.com/ticket/32101>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: Dulmandakh | Owner: nobody
Type: New feature | Status: closed
Component: Core (Other) | Version: 3.1
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: contrib.sessions => Core (Other)
* type: Bug => New feature
Comment:
I don't think that Django should include hooks based on user agents for
detecting bugs in old browsers. It sounds like a third-party package is
the best way to proceed.
You can start a discussion on DevelopersMailingList if you don't agree.
--
Ticket URL: <https://code.djangoproject.com/ticket/32101#comment:1>