#36991: LookupError crash (HTTP 500) in parse_header_parameters() when 
Content-Type
header contains RFC 2231 parameter with invalid encoding name
-------------------------------------+-------------------------------------
     Reporter:  claok                |                    Owner:  Dinesh
                                     |  Thumma
         Type:  Bug                  |                   Status:  closed
    Component:  HTTP handling        |                  Version:  5.1
     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 Jacob Walls <jacobtylerwalls@…>):

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

Comment:

 In [changeset:"dc467fdc3b5744cec71fab876c23a14013e2510b" dc467fdc]:
 {{{#!CommitTicketReference repository=""
 revision="dc467fdc3b5744cec71fab876c23a14013e2510b"
 Fixed #36991 -- Raised BadRequest for invalid encodings in Content-Type
 headers.
 }}}
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36991#comment:7>
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 view this discussion visit 
https://groups.google.com/d/msgid/django-updates/0107019db67065e7-603aafdd-4fa5-4322-80fe-d936efd1b912-000000%40eu-central-1.amazonses.com.

Reply via email to