#33522: Unexpected behaviour when logging in
-------------------------------------+-------------------------------------
Reporter: Michael | Owner: nobody
Type: New feature | Status: closed
Component: contrib.auth | Version: 4.0
Severity: Normal | Resolution: invalid
Keywords: authentication log | Triage Stage:
in CSRF token | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Michael):
Sorry yes that would be pointless.
With the "SameSite: Lax", and some JavaScript to set the X-CSRFToken
header, and not use GZIP for HTML responses (I think the masked CSRF Token
is to counter BREACH attacks), I think it would mitigate CSRF token
errors, and be just as secure. I understand the Django admin site is not
keen on JavaScript, so its up to custom code if one prefers that.
--
Ticket URL: <https://code.djangoproject.com/ticket/33522#comment:10>
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/068.b99ef58de86bd44ebf478f26fd0ee3aa%40djangoproject.com.
