#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: closed
Component: CSRF | Version: 1.11
Severity: Release blocker | Resolution: needsinfo
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 Nicola):
this bug is really difficult to track down, for my problem I added the
workaround in apache config, something like this:
{{{
ProxyPass /favicon.ico !
Alias /favicon.ico /path/to/favicon.ico
<Location "/favicon.ico">
Require all granted
</Location>
}}}
after this change the django admin site worked again, hope this helps
someone other.
I think I have this issue on my web site since a favicon is defined for
all pages but not /admin (django admin site) and so chrome try to get the
/favicon.ico for admin site (the favicon is in
/static/images/favicon.ico), django return 404 and admin site login does
not work.
A fix in django itself would be really appreciated, thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/28488#comment:23>
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.8be913d310272ce42ea000733826dbeb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
