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

Re: What is Content-Length?

From: Henrik Frystyk Nielsen <frystyk@w3.org>
Date: Wed, 17 Dec 1997 16:09:40 -0500
Message-Id: <>
To: Larry Masinter <masinter@parc.xerox.com>, Josh Cohen <joshco@microsoft.com>
Cc: "'koen@win.tue.nl'" <koen@win.tue.nl>, mogul@pa.dec.com, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/5008
At 10:43 12/17/97 PST, Larry Masinter wrote:
>We need to resolve the issue of content-length and cascaded
>transfer encodings quickly. We need two interoperable
>implementations of this 'feature', even if it is implicit in
>the spec, or else we should restrict the allowed set.

libwww is certainly designed to handle multiple transfer encodings as well
as multiple content encodings on client side. The application can register
new handlers for encodings dynamically - they just get plugged into the
read stream.

>I don't think we should explore too many degrees of freedom.

When a client says that it understands multiple encodings using TE, it
should also be able to plug them together.

I actually don't think we have to provide sanity rules here - there are
many other places in the spec where we expect people to use the "don't
forget to think" rule. The only rule we need is that a message must be self
delimiting according to section 4.4, but this is already stated there.

Henrik Frystyk Nielsen,
World Wide Web Consortium
Received on Wednesday, 17 December 1997 13:19:17 UTC

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