#28488: Django 1.11 to 1.11.4 raises CSRF verification failed if settings.DEBUG
is
False
-------------------------------------+-------------------------------------
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):
The traceback doesn't give me any ideas about the cause. I think you'll
need to add further logging in `django/middleware/csrf.py` to find the
root cause.
A large CSRF change between Django 1.8 and 1.11 is
5112e65ef2df1dbb95ff83026b6a962fb2688661. Perhaps you can test with Django
1.9 and 1.10 to help narrow the problem.
--
Ticket URL: <https://code.djangoproject.com/ticket/28488#comment:4>
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.fd72235a0351f6cb82cd77771a9511a0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
