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

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/