#35838: request.read() returns empty for Requests w/ Transfer-Encoding: Chunked
------------------------------------+--------------------------------------
Reporter: Klaas van Schelven | Owner: (none)
Type: Uncategorized | Status: new
Component: HTTP handling | Version: 5.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+--------------------------------------
Comment (by Klaas van Schelven):
> WSGI servers must handle any supported inbound “hop-by-hop” headers on
their own, such as by decoding any inbound Transfer-Encoding, including
chunked encoding if applicable.
That's the part that's relevant to the present discussion (I think it's
also the only part, but I might be wrong)
What do you take that to say w/ regards to the above? Because e.g.
Gunicorn "decodes" just fine (it parses the hex-coded chunk-lenghts and
removes those from the stream as seen by Django) as long as you don't
expect "decoding" to mean "also adds fake Content-Length header"
--
Ticket URL: <https://code.djangoproject.com/ticket/35838#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/010701928c58af41-a551fce7-b538-402b-9076-b2beb63249dd-000000%40eu-central-1.amazonses.com.
