#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 bcail):
> You can see in the ASGI spec mentioned in that ticket it says "a
response that is given to the server with no Content-Length may be chunked
as the server sees fit". Which is what is happening. Everything is
streaming into Django correctly. It just doesn't know how to handle a non-
existent content length.
I actually understand that to be talking about responses coming *from*
Django (or another ASGI app) back to the ASGI server, not a request going
into Django.
--
Ticket URL: <https://code.djangoproject.com/ticket/35289#comment:6>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018e519ef145-bd1403f5-3316-4fb4-86a5-bdff477189e6-000000%40eu-central-1.amazonses.com.
