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

RE: What is Content-Length?

From: David W. Morris <dwm@xpasc.com>
Date: Wed, 17 Dec 1997 13:21:48 -0800 (PST)
To: Paul Leach <paulle@microsoft.com>
Cc: Josh Cohen <joshco@microsoft.com>, 'Larry Masinter' <masinter@parc.xerox.com>, "'koen@win.tue.nl'" <koen@win.tue.nl>, mogul@pa.dec.com, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Message-Id: <Pine.GSO.3.96.971217130925.23263K-100000@shell1.aimnet.com>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/5009

On Wed, 17 Dec 1997, Paul Leach wrote:

> Before we can just "resolve quickly", I'm worried about the possibility of
> existing implementations of (e.g.)
>    Content-Length: XXX
>    T-E: gzip
>    <gzipped stuff, XXX bytes long>
> which means that C-L is, defacto, the length of the message-body.
> Absent info on such an implementation(s), we can invent lots of internally
> consistent schemes, but they wouldn't conform to existing (presumably) RFC
> 2068 compliant implementations.

But then "Transfer-encoding: gzip" would be an extension to RFC2068. 
It seems to me that by the rules, an extension we haven't heard about
can be ignored as experimental and subject to the risk of requiring
adjustment as standards change.

Received on Wednesday, 17 December 1997 13:28:17 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:21 UTC