#32757: CSRF cookies are not issued once expired if the session cookie is still
valid
--------------------------------------+----------------------------------
Reporter: Luke Sapan | Owner: nobody
Type: Bug | Status: new
Component: CSRF | Version: 3.2
Severity: Normal | Keywords: csrf, cookie age
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
--------------------------------------+----------------------------------
Currently, if someone sets `SESSION_COOKIE_AGE` beyond a year without also
extending `CSRF_COOKIE_AGE`, their users are going to start running into
CSRF errors. There may be a reason for it, but Django won't issue a new
CSRF token once it expires if the user still has a valid session cookie.
I'm not sure if there's a security reason for this (I can't think of one),
but even if there is, it would make sense to add a warning during startup
if `SESSION_COOKIE_AGE > CSRF_COOKIE_AGE`.
--
Ticket URL: <https://code.djangoproject.com/ticket/32757>
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/049.f62b60e0703bb732243a9f4613c08bef%40djangoproject.com.
