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

Re: What is Content-Length?

From: Roy T. Fielding <fielding@kiwi.ics.uci.edu>
Date: Wed, 17 Dec 1997 12:59:34 -0800
To: Larry Masinter <masinter@parc.xerox.com>
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Message-Id: <9712171301.aa18111@paris.ics.uci.edu>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/5007
>* chunked is only allowed once, as the last transfer encoding
>  applied.

okay by me

>* 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, that's unnecessarily restrictive.

>* 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).

No, that would violate the whole model.  multipart types are payload
in HTTP.  Furthermore, MIME does not allow T-Es within body-parts,
only C-T-Es.

>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.

That would be a new requirement.  Non-delimited response bodies are
still allowed in HTTP/1.1.  I do agree that if a non-delimited T-E
is used, chunked should be required on top.

Received on Wednesday, 17 December 1997 13:16:29 UTC

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