#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
-------------------------------------+-------------------------------------
Comment (by Florian Apolloner):
I've attached a patch, it is still not perfect and the underlying problem
will still be there if there is a middleware doing something stupid before
the CSRF middleware is run (ie run the http404 handler in
`process_request`).
As for
https://github.com/django/django/commit/eef95ea96faef0b7dbbe0c8092202b74f68a899b
#diff-a3be722ce2831a8d11438021d44cedf1L200 -- I was wrong there, it is
afaik not needed since if the "CSRF_COOKIE_USED" basically takes care of
that too.
--
Ticket URL: <https://code.djangoproject.com/ticket/28488#comment:29>
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.fd1cd61c65505b536876bda600fd95c3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
