Re: Porting T-E to HTTP/2: Reasons Against from Martin Thomson on 2014-04-11 (ietf-http-wg@w3.org from April to June 2014)

From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 11 Apr 2014 11:22:32 -0700
To: Roland Zink <roland@zinks.de>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <CABkgnnVsAtWc=N-89H8aL8PA=c22UsUBMMF8x-7pObqsZtya5A@mail.gmail.com>

On 11 April 2014 10:53, Roland Zink <roland@zinks.de> wrote:
> Hi Martin,
>
> So the following text was modified?
>
> Roland
>
> 9.3 GZip Content-Encoding
>
> Clients MUST support gzip compression for HTTP response bodies. Regardless
> of the value of the accept-encoding header field, a server MAY send
> responses with gzip encoding.

draft-mbelshe-httpbis-spdy-00 included the following text:

      User-agents MUST support gzip compression.  Regardless of the
      Accept-Encoding sent by the user-agent, the server may always send
      content encoded with gzip or deflate encoding.

That has been replaced with the section you cite part of.

Received on Friday, 11 April 2014 18:23:00 UTC