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

Re: i28 proposed replacement text

From: Yves Lafon <ylafon@w3.org>
Date: Tue, 3 Jun 2008 12:34:27 -0400 (EDT)
To: Henrik Nordstrom <henrik@henriknordstrom.net>
Cc: Jamie Lokier <jamie@shareable.org>, Joe Orton <joe@manyfish.co.uk>, Mark Nottingham <mnot@mnot.net>, Brian Smith <brian@briansmith.org>, ietf-http-wg@w3.org
Message-ID: <Pine.LNX.4.64.0806031220200.12469@ubzre.j3.bet>

On Tue, 3 Jun 2008, Henrik Nordstrom wrote:

> I don't see why as this isn't a guaranteed even if chunking is used in
> the hop to the receiver.
>
> Chain may be
>
> server [Connection: close, no TE] -> proxy [Transfer-Encoding: chunked]
> -> recipient
>
> In which case receiving a properly terminated chunked encoding says
> nothing about if the message was truncated in transit or not.

Well, in that case, it would be better for the proxy to figure out there 
is a potential error from server to proxy and to something clever (cutting 
the connection without sending the last chunk ?) to signal this.

> Denying upgrading from Connection: close to Transfer-Encoding: chunked
> would work around this, but at a significant performance penalty and
> also uncertain as such upgrading is actively done by deployed RFC2616
> compliant implementations.
>
> 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.

Integrity is also a hop-by-hop property. For end-to-end, Content-MD5 and 
others are here to help.

>
> But I am in favor for stating that if the transfer encoding could not be
> properly decoded (decompression error in gzip/deflate, missing end chunk
> in chunked etc..) or if network errors is detected while receiving the
> message (i.e. read error or similar) the message SHOULD be considered
> invalid and the connection closed. Implementations MUST NOT try to
> continue using a connection after a transport error including
> transfer-encoding related issues.
>
> Regards
> Henrik
>

-- 
Baroula que barouleras, au tiéu toujou t'entourneras.

         ~~Yves
Received on Tuesday, 3 June 2008 16:35:00 GMT

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