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

Re: i28 proposed replacement text

From: Yves Lafon <ylafon@w3.org>
Date: Wed, 2 Jul 2008 13:05:36 -0400 (EDT)
To: Henrik Nordstrom <henrik@henriknordstrom.net>
Cc: ietf-http-wg@w3.org
Message-ID: <Pine.LNX.4.64.0806240912330.14595@ubzre.j3.bet>

To sum up, the current text should not be changed, as it is valid to cut 
the connection to signal the end of the tranfer, even if Transfer-Encoding 
is used _without_ using chunked encoding.

However, if it was raised as an issue, it deserves clarification, and most 
probably a warning.

So, in 4.4, item 2:

<<<
2.  If a Transfer-Encoding header field (Section 8.7) is present,
        then the transfer-length is defined by use of the "chunked"
        transfer-coding (Section 3.4), unless the message is terminated
        by closing the connection.
>>>
replaced by
<<<
2.  If a Transfer-Encoding header field (Section 8.7) is present, and
        the "chunked" transfed-coding (Section 3.4) is used, the
        transfer-length is defined by the use of this transfer-coding.
        If the "chunked" transfer-coding is not present, the
        transfer-length is defined by [the emitter] closing the connection.

        Warning: If the transfer-length is defined by closing the
        connection, the transfer-coding used might not have characteristics
        to ensure that the  sender and the recipient sent/received the same
        message.
>>>

As it doesn't make much sense for a client to close the connection after 
sending an entity using TE without chunk, we can just replace [the 
emitter] (in [] just to show it needs a better wording) by 'the server'.
Cheers,


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

         ~~Yves
Received on Wednesday, 2 July 2008 17:06:12 GMT

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