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

Re: Support for gzip at the server #424 (Consensus Call)

From: Matthew Kerwin <matthew@kerwin.net.au>
Date: Tue, 29 Apr 2014 16:38:12 +1000
Message-ID: <CACweHNDnviX0wbGg=sPqOBQXZCPHrU_8WVKHeT=K+rcZ=s-mzg@mail.gmail.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Julian Reschke <julian.reschke@gmx.de>, Mark Nottingham <mnot@mnot.net>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
On 29 April 2014 16:33, Willy Tarreau <w@1wt.eu> wrote:

>
>
> In HTTP/1.1, we have 100-continue which would be the perfect fit for this.
> The client waits for the server's agreement to send contents, and the
> server could advertise its supported compression algorithms (both T-E and
> C-E) in the 100-continue. And the benefit is that if an intermediary needs
> to scan this content, it sends the 100 itself and will advertise what it
> supports.
>
> I don't know how we could translate that into 2.0 though.
>
>
​T-E negotiation is replaced by a setting, and settings are sent as soon as
the connection is established, so that's already solved.​ I don't know how
a server could advertise support for content-encoded data within the
protocol.

-- 
  Matthew Kerwin
  http://matthew.kerwin.net.au/
Received on Tuesday, 29 April 2014 06:38:39 UTC

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