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

Re: problem with chunked encoding in http1.1

From: Patrick McManus <mcmanus@appliedtheory.com>
Date: Thu, 5 Jul 2001 14:04:26 -0400
To: "Nathan J. Yoder" <njyoder@hotmail.com>
Cc: http-wg@cuckoo.hpl.hp.com
Message-ID: <20010705140426.A32189@AppliedTheory.com>
chunked is also required on any message that has any transfer-encoding
other than chunked or identity (e.g. gzip). This removes ambiguity of
whether content-length refers to the encoded or unencoded


[Nathan J. Yoder: Thu, Jul 05, 2001 at 01:48:39PM -0400]
> Ignore the second part of the last message, I didn't read the full response
> in one of the e-mails.  That's right, chunked transfer enocoding is good for
> messages of indeterminate length (like CGI generated responses), else it
> would require caching the message in memory before sending (to determine the
> length).
Received on Thursday, 5 July 2001 19:13:50 UTC

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