#32817: Include in CsrfViewMiddleware's bad CSRF token message where the token 
is
from
-------------------------------------+-------------------------------------
     Reporter:  Chris Jerdonek       |                    Owner:  Chris
         Type:                       |  Jerdonek
  Cleanup/optimization               |                   Status:  closed
    Component:  CSRF                 |                  Version:  dev
     Severity:  Normal               |               Resolution:  fixed
     Keywords:                       |             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 Mariusz Felisiak <felisiak.mariusz@…>):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"fcb75651f9b8c2f76ec037f1a68a0e5c99263d8c" fcb7565]:
 {{{
 #!CommitTicketReference repository=""
 revision="fcb75651f9b8c2f76ec037f1a68a0e5c99263d8c"
 Fixed #32817 -- Added the token source to CsrfViewMiddleware's bad token
 error messages.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/32817#comment:9>
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.27381ed46b38892c558186241d1e5ea5%40djangoproject.com.

Reply via email to