W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1998

Content-Encoding and Content-Type in trailer?

From: Perry R. Ross <pross@platinum.com>
Date: Mon, 4 May 1998 19:47:21 +0100 (BST)
Message-Id: <354E0C3C.482F2F8E@platinum.com>
To: http-wg@cuckoo.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/106
I have searched the open issues and believe that this is a new issue.

It seems that including Content-Encoding or Content-Type in the
trailer of a chunked transfer would be incorrect.  Allowing this would
require that the entire message body be buffered until the trailer is
received, so that the content codings may be removed, or the content
interpreted.  There doesn't seem to be any need for these headers to
appear in the trailer, since this information should be known before the

message transfer begins.  As far as I can tell, libwww would not
process a message with Content-Encoding headers in the trailer.

If I am incorrect in this, or if you are not soliciting public comments
at this time, please accept my apologies.

Thank you.
Perry R. Ross     pross@platinum.com     800-526-9096 X4986
Received on Tuesday, 5 May 1998 04:39:47 UTC

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