#35838: Support Requests with Transfer-Encoding: Chunked
------------------------------------+------------------------------------
Reporter: Klaas van Schelven | Owner: (none)
Type: New feature | Status: new
Component: HTTP handling | Version: 5.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+------------------------------------
Changes (by Sarah Boyce):
* cc: Natalia Bidart, Claude Paroz (added)
* stage: Unreviewed => Accepted
* summary:
request.read() returns empty for Requests w/ Transfer-Encoding:
Chunked
=> Support Requests with Transfer-Encoding: Chunked
* type: Uncategorized => New feature
Comment:
I think historically there has been an assumption that Content-Length will
always be present (see tickets such as #3057)
As I can't find any reference of support for Transfer-Encoding: Chunked
being added, I believe we just don't have support for it and we should
treat this as a new feature to Django
Tentatively accepted. We could also repurpose #35289 in order to add
Transfer-Encoding: Chunked support more generally and mark this as a
duplicate
Will cc a couple of folks involved in previous discussions to see if they
agree
--
Ticket URL: <https://code.djangoproject.com/ticket/35838#comment:12>
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/010701928ef55ccb-42add877-0d08-4245-bba0-87cb4df58ab1-000000%40eu-central-1.amazonses.com.
