#36931: Unhandled LookupError in multipart parser when RFC 2231 encoding name is
invalid
-------------------------------------+-------------------------------------
Reporter: sammiee5311 | Owner:
Type: | sammiee5311
Cleanup/optimization | Status: closed
Component: HTTP handling | Version: 6.0
Severity: Normal | Resolution: fixed
Keywords: multipart parser | Triage Stage: Ready for
LookupError RFC2231 | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls <jacobtylerwalls@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"e84dc8715e91d51364ba6bda2b2fb07e7a8b750e" e84dc871]:
{{{#!CommitTicketReference repository=""
revision="e84dc8715e91d51364ba6bda2b2fb07e7a8b750e"
Fixed #36931 -- Handled LookupError in multipart parser for invalid RFC
2231 encoding.
Added LookupError to the except clause so invalid headers are silently
skipped, consistent with other malformed header handling.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36931#comment:10>
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/0107019c90f7dceb-bfcfec70-c174-42a1-8741-da596a5ab242-000000%40eu-central-1.amazonses.com.
