#26628: CSRF violations should be logged
-------------------------------+--------------------------------------
Reporter: jacobian | Owner: nobody
Type: New feature | Status: closed
Component: CSRF | Version: 1.9
Severity: Normal | Resolution: worksforme
Keywords: csrf security | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by mallyvai):
Hi Tim,
Definitely think it's a good idea to add to the docs.
My original thinking was that it would be a more sensible default to log
this as a security exception and use the django.security loggers (i'm not
100% sure about how that's wired up), since CSRFs are meant to be an
explicit security measure. It seems to be logged as a generic
logger.warning right now.
--
Ticket URL: <https://code.djangoproject.com/ticket/26628#comment:3>
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/066.44b850ebd21882226385398d25ccbe93%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
