Re: [Django] #26628: Log CSRF failures to django.security instead of django.request

[Django]

#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 ):

 * 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: 
Django 
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.81aa15bfd4363916b45b87c33c7a5a53%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26628: Log CSRF failures to django.security instead of django.request

[Django]

#26628: Log CSRF failures to django.security instead of django.request
--+
 Reporter:  jacobian  |Owner:  Hwesta
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  CSRF  |  Version:  1.9
 Severity:  Normal|   Resolution:
 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 timgraham):

 * needs_better_patch:  1 => 0


--
Ticket URL: 
Django 
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.ae69c2293b7cd063735334f25277ad5c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26628: Log CSRF failures to django.security instead of django.request (was: Log CSRF failures to django.security by default.)

[Django]

#26628: Log CSRF failures to django.security instead of django.request
--+
 Reporter:  jacobian  |Owner:  Hwesta
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  CSRF  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  csrf security | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_docs:  1 => 0
 * has_patch:  0 => 1
 * component:  Documentation => CSRF
 * needs_better_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/6707 PR] with comments for
 improvement.

--
Ticket URL: 
Django 
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.9b5d4115a344791ef86b6cffa34c2c45%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.