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

Re: What is Content-Length?

From: Larry Masinter <masinter@parc.xerox.com>
Date: Wed, 17 Dec 1997 10:43:20 PST
Message-Id: <34981D48.CBAA347@parc.xerox.com>
To: 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/5005
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.

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

* chunked is only allowed once, as the last transfer encoding
* before chunked is applied, only one T-E should be sent,
  but recipients should accept all combinations (as long as
  there are no duplicates).
* no T-E's other than 'chunked' may be applied to multipart/
  content-types, but T-Es are allowed within a multipart type
  (e.g., multipart/byte-ranges, multipart/form-data).

The entire transmission is required to be either with content-length
or else self-delimited where multipart is the only self-delimited
media type, but chunked, gzip are self-delimited T-Es.

Received on Wednesday, 17 December 1997 12:43:04 UTC

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