#26628: Log CSRF failures to django.security instead of django.request
--------------------------------------+------------------------------------
Reporter: jacobian | Owner: Hwesta
Type: Cleanup/optimization | Status: closed
Component: CSRF | Version: 1.9
Severity: Normal | Resolution: fixed
Keywords: csrf security | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"55fec16aafed30a9daa06d6ecdf8ca3ad361279e" 55fec16a]:
{{{
#!CommitTicketReference repository=""
revision="55fec16aafed30a9daa06d6ecdf8ca3ad361279e"
Fixed #26628 -- Changed CSRF logger to django.security.csrf.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26628#comment:14>
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.81aa15bfd4363916b45b87c33c7a5a53%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
