- From: Willy Tarreau <w@1wt.eu>
- Date: Fri, 20 Jul 2012 14:58:04 +0200
- To: Amos Jeffries <squid3@treenet.co.nz>
- Cc: Osama Mazahir <OSAMAM@microsoft.com>, Roberto Peon <grmocg@gmail.com>, Julian Reschke <julian.reschke@gmx.de>, Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>, Adrien de Croy <adrien@qbik.com>, Poul-Henning Kamp <phk@phk.freebsd.dk>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
On Fri, Jul 20, 2012 at 10:44:16PM +1200, Amos Jeffries wrote: > Part 1 section 3.3.3 point #5. In all of those cases content-length > amount of bytes MUST be sent or the connection aborted. OK, too much noise from me then, sorry. > 417 is a final response to that initial request. Therefore the server > drains the content-length body and connection re-use can begin. Client > is responsible for aborting the connection or padding with disposable > garbage bytes. At no point can the client send content-length then > re-use the connection earlier. That's fine then. Thanks for the pointer, Willy
Received on Friday, 20 July 2012 12:58:52 UTC