#30737: Incorrectly encoded headers can yield uncaught UnicodeDecodeError
-------------------------------+--------------------------------------
Reporter: Mark Gordon | Owner: nobody
Type: Bug | Status: closed
Component: HTTP handling | Version: master
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by felixxm):
* status: new => closed
* resolution: => invalid
* version: 2.2 => master
* component: Uncategorized => HTTP handling
* easy: 1 => 0
Comment:
Thanks for this report, however `parse_header` is a part of internal API
that expects an ASCII-encoded bytes (see
[https://github.com/django/django/blob/a44d80f88e22eda24dacef48e368895ebea96635/django/http/multipartparser.py#L70-L73
an example]). You can raise an issue in DRF if you think that there is any
in the way how they handle/use it.
Closing per TicketClosingReasons/UseSupportChannels.
--
Ticket URL: <https://code.djangoproject.com/ticket/30737#comment:1>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/064.85378cc42be5e74357ea9007ddc99e63%40djangoproject.com.
