#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 Klaas van Schelven):
> Given that both WSGI and ASGI specify that the server de-chunks the
request, I'm not sure what else would be needed here?
whatever the precise definition (spec) that the first part of that
sentence implies... "what else would be needed here" can be (and was)
answered by me as "don't silently throw away request bodies when Content-
Length is missing"
--
Ticket URL: <https://code.djangoproject.com/ticket/35838#comment:15>
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 visit
https://groups.google.com/d/msgid/django-updates/01070192badb6c36-9715beeb-bbf4-4cf1-ab92-f0f28fc50f11-000000%40eu-central-1.amazonses.com.
