#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
------------------------------------+------------------------------------
Comment (by Carlton Gibson):
> …add Transfer-Encoding: Chunked support more generally and mark this as
a duplicate.
They're certainly both closely related. Django receives the de-chunked
request, but then doesn't handle it as expected (because of the missing
Content Length header).
> ...support more generally...
Given that both WSGI and ASGI specify that the server de-chunks the
request, I'm not sure what else would be needed here? 🤔
--
Ticket URL: <https://code.djangoproject.com/ticket/35838#comment:13>
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/010701928eff9e19-8446ad6b-240a-4c16-ae66-c27ccde0ca7d-000000%40eu-central-1.amazonses.com.
