#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 see different csrfmiddlewaretoken values after each refresh but
the value of csrfmiddlewaretoken doesn't match with the csrftoken cookie
[...]
Turns out I was reading an older version of the document and this behavior
is expected in Django 1.11.
Also, I get 403 even if there was no 404 request in the middle so I'm
beginning to think that my problem is different than this ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/28488#comment:38>
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.38ef8f703b4c0a70fb09f7cab9d4100b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
