#35289: Chunked transfer encoding is not handled correctly by MultiPartParser
-------------------------------------+-------------------------------------
Reporter: Kyle Agronick | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: 5.0
Severity: Normal | Resolution:
Keywords: transfer-encoding, | Triage Stage:
chunked, multi-part | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Kyle Agronick):
I can confirm that just by making a middleware that does
{{{
if request.headers["Transfer-Encoding"] == "chunked" and
"CONTENT_LENGTH" not in request.META:
request.META["CONTENT_LENGTH"] = "1"
}}}
everything gets parsed correctly even though the `CONTENT_LENGTH` is much
more than 1.
Maybe this issue went undetected for so long because WSGI does not have
good support for chunked transfer encoding. But ASGI does.
--
Ticket URL: <https://code.djangoproject.com/ticket/35289#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/0107018e2ed66c59-a15689b0-3510-4c91-916d-9706a1444bbc-000000%40eu-central-1.amazonses.com.
