#35289: Chunked transfer encoding is not handled correctly by MultiPartParser
-------------------------------------+-------------------------------------
Reporter: Kyle Agronick | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: dev
Severity: Normal | Resolution:
Keywords: transfer-encoding, | Triage Stage: Accepted
chunked, multi-part |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by bcail):
> request body is correctly dechunked before being passed off to Django
If a request body is dechunked, should the Transfer-Encoding header still
be set to "chunked" and the Content-Length header be missing? Would it
make sense to change those if the request body is dechunked?
--
Ticket URL: <https://code.djangoproject.com/ticket/35289#comment:9>
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/0107018e52187ce4-db9c9145-70b3-4325-a159-b5b22d13d215-000000%40eu-central-1.amazonses.com.
