#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):
> RFC2616 describes how to ​decode a chunked request:
> This looks to me like the WSGI server should set the Content-Length
header
That is indeed one interpretation, but I'm not sure it's the only valid
one. In the quoted RFC Content-Length is calculated, but the RFC does not
say this should be translated into a header by a wsgi server (obviously,
since the RFC doesn't deal with WSGI).
--
Ticket URL: <https://code.djangoproject.com/ticket/35838#comment:17>
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/01070192c25dc914-20707708-0d93-4b17-a17d-550cc400062f-000000%40eu-central-1.amazonses.com.
