W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 1997

Re: Implementation Experience Content Encoding

From: Scott Lawrence <lawrence@agranat.com>
Date: Fri, 01 Aug 1997 15:33:15 -0400
Message-Id: <199708011933.PAA09696@devnix.agranat.com>
To: mcmanus@appliedtheory.com
Cc: Scott Lawrence <lawrence@agranat.com>, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/4062

>>>>> "PM" == Patrick McManus <mcmanus@appliedtheory.com> writes:

PM> That's nice for you, but my content has a type of text/plain so I want
PM> to label it like that.  14.3 of the current draft tells me

PM>             If no Accept-Encoding field is present in a request, the
PM>             server MAY assume that the client will accept any content
PM>             coding....

PM> and I don't have an identity version of my resource hanging
PM> around.. (I deleted it because in this bizarre case disk space is
PM> mighty precious) so I sent back gzip and all hell broke loose on a
PM> couple mighty popular windows browsers.

PM> So am I doing something wrong, or is the spec misleading with its
PM> note?

  The spec says you MAY assume that the client will accept any
  encoding; it doesn't promise that will work, or place any
  requirement on clients to do anything about it.  If I were you I'd
  add gunzip-on-the-fly to my server so that you can send real

Scott Lawrence           EmWeb Embedded Server       <lawrence@agranat.com>
Agranat Systems, Inc.        Engineering            http://www.agranat.com/
Received on Friday, 1 August 1997 12:34:38 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:03 UTC