W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2008

Re: i28 proposed replacement text

From: Jamie Lokier <jamie@shareable.org>
Date: Tue, 3 Jun 2008 13:09:00 +0100
To: Henrik Nordstrom <henrik@henriknordstrom.net>
Cc: Yves Lafon <ylafon@w3.org>, Joe Orton <joe@manyfish.co.uk>, Mark Nottingham <mnot@mnot.net>, Brian Smith <brian@briansmith.org>, ietf-http-wg@w3.org
Message-ID: <20080603120900.GB28905@shareable.org>

Henrik Nordstrom wrote:
> Integrity is not a property of the transport. The transport is
> hop-by-hop and must only guarantee internal consistency, allowing
> unambigious parsing of the data stream. Integrity checks should be done
> at the message level.

True, but there is no practical mechanism in HTTP at the moment to
assure even the most basic message integrity: that you received all of it.

Content-MD5 is not useful for dynamically produced entities.
As a trailer it might be possible, but how compatible is that?

Content-Length, even, cannot be used.

Not even for static content.  When the server does provide
Content-Length, in your own example the proxy->client hop removes
Content-Length.

I'm thinking that the solution to these is allowing Content-Length in
a chunked trailer, and Content-MD5 too.

-- Jamie
Received on Tuesday, 3 June 2008 12:09:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:48 GMT