#26628: Log CSRF failures to django.security by default.
--------------------------------------+------------------------------------
Reporter: jacobian | Owner: Hwesta
Type: Cleanup/optimization | Status: assigned
Component: Documentation | Version: 1.9
Severity: Normal | Resolution:
Keywords: csrf security | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by carljm):
I guess I'm not too concerned about back-compat, because it seems it would
only be an issue in a case where someone has configured logging to watch
`django.request` but ignore `django.security`, which seems like a pretty
strange choice. But I also don't feel strongly. I'd be inclined to merge
the doc fix that Hwesta has already submitted
(https://github.com/django/django/pull/6694/files) but as a `Refs`, and
leave this open for further discussion of the actual logger change.
--
Ticket URL: <https://code.djangoproject.com/ticket/26628#comment:8>
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/066.382f546a3936c938edcec7c13c68b93c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
