#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: master
Severity: Release blocker | Resolution:
Keywords: csrf failed | Triage Stage: Accepted
settings debug false production |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Berker Peksag):
I have the same problem, but disabling the custom 404 handler didn't work
for me as described in #28143 (closed as a duplicate of this issue)
> Removing the custom 404 view from urls.py, or setting DEBUG to True
(obviously), fixes the Django admin failed csrf error.
Test URL: https://staging.python.org/admin/
Source code: https://github.com/python/pythondotorg
Installation document: https://pythondotorg.readthedocs.io/install.html
--
Ticket URL: <https://code.djangoproject.com/ticket/28488#comment:34>
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.2ca5005f1e83e8cdbbaa600caa055f42%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
