#35289: Chunked transfer encoding is not handled correctly by MultiPartParser
-------------------------------------+-------------------------------------
     Reporter:  Kyle Agronick        |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  HTTP handling        |                  Version:  5.0
     Severity:  Normal               |               Resolution:
     Keywords:  transfer-encoding,   |             Triage Stage:
  chunked, multi-part                |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):

 * cc: Carlton Gibson (added)

Comment:

 Hello Kyle!

 [https://datatracker.ietf.org/doc/html/rfc2616#section-4.4 RFC 2616] is
 obsoleted by [https://datatracker.ietf.org/doc/html/rfc7230 RFC 7230]
 which in turn is obsoleted by RFC 9110 and RFC 9112, and as far as I read
 in [https://datatracker.ietf.org/doc/html/rfc9112#message.body RFC 9112],
 both headers could co-exist (but `Content-Length` should be ignored if
 `Transfer-Encoding` is sent):

 > Early implementations of Transfer-Encoding would occasionally send both
 a chunked transfer coding for message framing and an estimated Content-
 Length header field for use by progress bars. This is why Transfer-
 Encoding is defined as overriding Content-Length, as opposed to them being
 mutually incompatible.

 But, at the same time, I found an analogous issue for
 [https://github.com/django/daphne/issues/371 Daphne], and I see that you
 have just commented on the other referenced Daphne issue, so this may be a
 valid issue. I will cc/Carlton to confirm before fully triaging.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35289#comment:5>
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/0107018e5197f137-62bfab67-42b8-408a-81e6-a65dd6036908-000000%40eu-central-1.amazonses.com.

Reply via email to