Re: legality of Transfer-Encoding: chunked bodies in HTTP/2 from Martin Thomson on 2014-08-05 (ietf-http-wg@w3.org from July to September 2014)

From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 5 Aug 2014 14:35:10 -0700
To: Osama Mazahir <OSAMAM@microsoft.com>
Cc: Zhong Yu <zhong.j.yu@gmail.com>, Johnny Graettinger <jgraettinger@chromium.org>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <CABkgnnXRNNDZz8-r5tyVw9TgWm2Q__-XTx8edWXX9uG47ZDxog@mail.gmail.com>

On 5 August 2014 14:00, Osama Mazahir <OSAMAM@microsoft.com> wrote:
> +1 for allowing Chunked.

HTTP/2 is inherently chunked.  You don't have to send Content-Length,
though we do like to encourage it.  Stripping the decoration (the
chunking) is necessary if you want to make DATA frames.  Otherwise we
have HTTP/2 implementations needing to know about the details (and
corresponding mess) of HTTP/1.1 framing.

When it comes to reforming into 1.1, you can make your own assessment
about how to translate.  If you have content-length, then chunked
encoding isn't neccessary, even if it was originally chunked.

Received on Tuesday, 5 August 2014 21:35:38 UTC