#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):
Side-note: I found stumbling upon this bug quite surprising: you would
think that requests w/ chunked transfer-encoding are used often enough for
this to have surfaced more broadly _at some point_, but I couldn't find
much more than the things I already linked. Perhaps it's not broadly used?
Or perhaps it is, but in contexts where it is Django is always behind some
proxy that removes it, and sends the WSGI server (and Django) something
"more plain"?
--
Ticket URL: <https://code.djangoproject.com/ticket/35838#comment:4>
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/010701928c24a45a-841f3e58-d90b-4d34-945a-d44357db7e9a-000000%40eu-central-1.amazonses.com.
