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

Re: p2: Expect: 100-continue and "final" status codes

From: Adrien W. de Croy <adrien@qbik.com>
Date: Wed, 24 Apr 2013 08:34:30 +0000
To: "Amos Jeffries" <squid3@treenet.co.nz>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Message-Id: <em9da5a567-6b0f-4b8c-b113-080fb794c5e2@bombed>

------ Original Message ------
From: "Amos Jeffries" <squid3@treenet.co.nz>

>The problem comes with intermediaries. How are they to know the bytes 
>following were the original advertised payload or not? the status from 
>server has no guarantee of arriving after the client payload starts 

Any bytes after the request + headers but not including advertised 
payload must be payload.  There's no other option apart from closing 
(e.g. another request is not an option, since the first message has not 
been sent until any advertised payload is sent, or if it's chunked a 0 
chunk has been sent).

So there's no ambiguity and no need for an intermediary to have 
previously received the server response (initial or otherwise).


>The only way to guarantee safety on the connection is to close it or 
>always send payload.
Received on Wednesday, 24 April 2013 08:34:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:12 UTC