- From: Matthew Kerwin <matthew@kerwin.net.au>
- Date: Fri, 21 Feb 2014 15:39:57 +1000
- To: Amos Jeffries <squid3@treenet.co.nz>
- Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Received on Friday, 21 February 2014 05:40:26 UTC
On 21 February 2014 15:32, Amos Jeffries <squid3@treenet.co.nz> wrote: > On 21/02/2014 5:13 p.m., Mark Nottingham wrote: > > > > So, what the current text *really* says is that servers can ignore the > 'identity' content-encoding when it appears alone in the request. > > Huh? identiy coding being explicitly sent is a non-empty field. > > I read that as saying only an empty header means "anything goes, YMMV", > and * value meaning "anything goes, honest, I promise" > The other current text, in HTTP/2, that says: | Clients MUST support gzip compression for HTTP request bodies. | Regardless of the value of the accept-encoding header field, a server | MAY send responses with gzip or deflate encoding. IOW "Accept-Encoding: identity" can be ignored, because you can still gzip the response. -- Matthew Kerwin http://matthew.kerwin.net.au/
Received on Friday, 21 February 2014 05:40:26 UTC