#28488: Django 1.11+ raises CSRF verification failed if settings.DEBUG is False
and
an intermediate 404 page is requested
-------------------------------------+-------------------------------------
Reporter: Ruben Alves | Owner: nobody
Type: Bug | Status: new
Component: CSRF | Version: 1.11
Severity: Release blocker | Resolution:
Keywords: csrf failed | Triage Stage:
settings debug false production | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* cc: Jay Cox (added)
Comment:
Jay, as the author of eef95ea96faef0b7dbbe0c8092202b74f68a899b, can you
look at this? It looks like before your patch, this condition in
`CsrfViewMiddleware.process_response()` prevented a CSRF token from being
set for the 404 requests:
{{{
if request.META.get("CSRF_COOKIE") is None:
return response
}}}
After the patch, a cookie is being set for those requests.
--
Ticket URL: <https://code.djangoproject.com/ticket/28488#comment:26>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.f1cf3b4caa7121a7a6f0de7865ad41a5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
