#23900: Section on Preventing header injection does not include some imports
-------------------------------------+-------------------------------------
     Reporter:  kevgathuku           |                    Owner:
         Type:                       |  kevgathuku
  Cleanup/optimization               |                   Status:  closed
    Component:  Documentation        |                  Version:  master
     Severity:  Normal               |               Resolution:  fixed
     Keywords:  BadHeaderError,      |             Triage Stage:  Ready for
  docs                               |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  1                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Baptiste Mispelon <bmispelon@…>):

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


Comment:

 In [changeset:"0d74209ef66111f29f122d5f5fdf8e2964890cc5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0d74209ef66111f29f122d5f5fdf8e2964890cc5"
 Fixed #23900 -- Added missing imports in code example.

 The Preventing header injection example included
 classes that are not imported.

 Thanks to Collin Anderson and Berker Peksağ for the
 reviews.
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/23900#comment:5>
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 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/068.c8eb49c6f79b2c086570ad6794103937%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to