#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):
> Does my PR fix it for you?
I can't reproduce the problem in development environment even if I set
`settings.DEBUG` to `False`. I applied your patch manually on the server
and unfortunately I still get 403 when I try to submit a form.
--
Ticket URL: <https://code.djangoproject.com/ticket/28488#comment:36>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.8dbcd7548bd8be809e80e038020eea01%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
