#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 Carlton Gibson):
This [https://github.com/django/daphne/issues/476#issuecomment-1557267731
comment on the related request-centred Daphne issue] suggests that that
request body is correctly dechunked before being passed off to Django. The
question we had there was "why it's not getting out of Django's
`HttpRequest._load_post_and_files()`" Kyle's suggestion looks on point:
the missing content length isn't an error (IIUC).
I'd guess here we'd would set expected content length to
`len(request.body)` if the Transfer-Encoding header field was set 🤔
--
Ticket URL: <https://code.djangoproject.com/ticket/35289#comment:7>
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/0107018e51b6e7a4-f71888e9-e908-4abf-a64d-244bec69cc81-000000%40eu-central-1.amazonses.com.
