- From: Amos Jeffries <squid3@treenet.co.nz>
- Date: Fri, 21 Feb 2014 18:32:26 +1300
- To: ietf-http-wg@w3.org
On 21/02/2014 5:13 p.m., Mark Nottingham wrote: > The other aspect of this is that HTTP already says: > >> A request without an Accept-Encoding header field implies that the >> user agent has no preferences regarding content-codings. Although >> this allows the server to use any content-coding in a response, it >> does not imply that the user agent will be able to correctly process >> all encodings. >> >> A server tests whether a content-coding for a given representation is >> acceptable using these rules: >> >> 1. If no Accept-Encoding field is in the request, any content-coding >> is considered acceptable by the user agent. > > ... > > <http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-26#section-5.3.4> > > 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" Amos
Received on Friday, 21 February 2014 05:33:09 UTC