- From: Adrien de Croy <adrien@qbik.com>
- Date: Thu, 26 Jan 2012 14:43:47 +1300
- To: Amos Jeffries <squid3@treenet.co.nz>
- CC: ietf-http-wg@w3.org
actually this raises the issue of aborting transfers. Currently to abort a chunked transfer, you must close the connection. (and this triggers all sorts of nasty buggy behaviour in browsers - most of which don't complain). It would be nice if the chunk header could signal an abort. On 26/01/2012 11:58 a.m., Amos Jeffries wrote: > 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 > > -- Adrien de Croy - WinGate Proxy Server - http://www.wingate.com WinGate 7 is released! - http://www.wingate.com/getlatest/
Received on Thursday, 26 January 2012 01:44:32 UTC