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

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

From: Mark Nottingham <mnot@mnot.net>
Date: Wed, 24 Apr 2013 13:32:16 +1000
Cc: ietf-http-wg@w3.org
Message-Id: <4805210C-9117-4E5E-9D95-9E9A12A0CE03@mnot.net>
To: Amos Jeffries <squid3@treenet.co.nz>

On 24/04/2013, at 12:41 PM, Amos Jeffries <squid3@treenet.co.nz> wrote:
>>> 
>>> I think we can give better advice than that. If a server responds with a final status code instead of 100 (Continue)
>>> 
>>> 1. The response must be the last response on the connection. The response should contain "Connection: close" header. After the response is written, the server must initiate a lingering close of the connection (p1#6.6).
>> That seems too restrictive; as long as the server reads the rest of the request properly (discarding it), it should be able to recover and reuse the connection.
> 
> 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 arriving.
> The only way to guarantee safety on the connection is to close it or always send payload.


True. 

--
Mark Nottingham   http://www.mnot.net/
Received on Wednesday, 24 April 2013 03:32:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:10 UTC