#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 Tim Graham):
Thanks for the sample project. I bisected the changed in behavior to
eef95ea96faef0b7dbbe0c8092202b74f68a899b which first appeared in Django
1.9, yet the report is about Django 1.11, so I'm not sure if everyone
reporting this issue is encountering the same problem. It looks like the
key to reproducing it is that the custom `handler404` uses `render()`
rather than `render_to_response()` or a plain `HttpResponse()`. I'll look
more later.
--
Ticket URL: <https://code.djangoproject.com/ticket/28488#comment:25>
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.b8405150a5ae7a87ebd155e3642eb427%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
