#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):
Sergio Campos (seocam) and I were just discussing this same issue at the
PyCon sprint (in the context of looking at the broader context in #26688).
I'm inclined to agree with mallyvai that this isn't just a doc bug -- we
should be logging CSRF failures to django.security by default. Updating
the ticket title accordingly -- please let me know if you don't agree, or
think this should be discussed on the mailing list.
--
Ticket URL: <https://code.djangoproject.com/ticket/26628#comment:6>
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.7ad6743ddd81d19c41150ba971d8a493%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
