W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2014

Re: Support for gzip at the server #424

From: Roberto Peon <grmocg@gmail.com>
Date: Thu, 13 Mar 2014 18:26:12 -0700
Message-ID: <CAP+FsNf9j-nKDz5wYcea5=McF9J9MOK8KgLPy3LdZDqaweU28w@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Ah I missed part of the original email-- yes, the decompressed content
length needs to be known.
That can be easily solved, though.
On Mar 13, 2014 6:24 PM, "Roberto Peon" <grmocg@gmail.com> wrote:

> Decompress, yes, buffer the entire body? No. Gzip can happily be
> stream-decompressed.
>
> -=R
> On Mar 10, 2014 2:03 AM, "Martin Thomson" <martin.thomson@gmail.com>
> wrote:
>
>> Discussion offline leads me to conclude that doing this would be bad idea.
>>
>> The basic problem is with 2->1.1 translation at intermediaries.  While
>> the HTTP/2 request might include a Content-Length, the gateway is
>> going to be forced to decompress and buffer the entire request body
>> before forwarding to a 1.1 server.
>>
>> This doesn't seem like a good outcome.  Maybe this is something to
>> defer to the version of HTTP/x that ships when most of the world is
>> already using HTTP/2.
>>
>>
Received on Friday, 14 March 2014 01:26:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:24 UTC