W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2012

Re: Rechartering HTTPbis

From: Amos Jeffries <squid3@treenet.co.nz>
Date: Thu, 26 Jan 2012 11:58:55 +1300
To: <ietf-http-wg@w3.org>
Message-ID: <66eee97e18fc32a5ae67e992e6c9ae98@treenet.co.nz>
On 26.01.2012 08:52, Poul-Henning Kamp wrote:
> In message <4F205B2E.5080407@qbik.com>, Adrien de Croy writes:
>
>>> * Option for specifying preliminary metadata in front of content 
>>> and
>>>    update it to final values after content.  This allows a server 
>>> to
>>>    Say this looks like "200=OK, 1Mbyte long, text/html, but hold 
>>> on..."
>>>    then send the object and update with "I was wrong, it was only 
>>> 800k.",
>>>    "Ohh, and btw, it expires in 4 seconds", "my disk failed, sorry: 
>>> 206".
>>
>>that will make life really hard for intermediaries.  When can you 
>> write
>>your cache index information, if information will be countermanded.
>
> Actually it will make it easier for some of them, for instance during
> ESI operations.
>
> It also means that we don't have to abandon a TCP connection just 
> because
> something went wrong with a object (ie: more separation of transport
> from content)

Provided that the trailer details are limited to transport meta data 
like your example case.

Altering that "text/html" to "image/jpeg" in the trailer or similar 
trick introduces a whole mess of security attacks I don't think we want 
to go near at this point.

AYJ
Received on Wednesday, 25 January 2012 22:59:20 GMT

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