#32101: Handle SameSite=None Known Incompatible Clients
--------------------------------------------+------------------------
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.
--
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/053.a993febbefd2fcf01b843156143e576c%40djangoproject.com.
