#24496: Check CSRF Referer against CSRF_COOKIE_DOMAIN
-------------------------------------+-------------------------------------
     Reporter:  mattrobenolt         |                    Owner:  Tim
                                     |  Graham <timograham@…>
         Type:  New feature          |                   Status:  closed
    Component:  CSRF                 |                  Version:  master
     Severity:  Normal               |               Resolution:  fixed
     Keywords:  csrf 1.9             |             Triage Stage:  Ready for
                                     |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):

 * status:  new => closed
 * owner:   => Tim Graham <timograham@…>
 * resolution:   => fixed


Comment:

 In [changeset:"b0c56b895fd2694d7f5d4595bdbbc41916607f45" b0c56b89]:
 {{{
 #!CommitTicketReference repository=""
 revision="b0c56b895fd2694d7f5d4595bdbbc41916607f45"
 Fixed #24496 -- Added CSRF Referer checking against CSRF_COOKIE_DOMAIN.

 Thanks Seth Gottlieb for help with the documentation and
 Carl Meyer and Joshua Kehn for reviews.
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/24496#comment:30>
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/070.5702c738c5ae2dda96b68f338a82aabb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to