- From: Mark Nottingham <mnot@mnot.net>
- Date: Tue, 28 May 2013 15:37:37 +1000
- To: Alex Rousskov <rousskov@measurement-factory.com>
- Cc: ietf-http-wg@w3.org
On 21/05/2013, at 2:44 AM, Alex Rousskov <rousskov@measurement-factory.com> wrote: > On 05/17/2013 05:28 AM, Ken Murchison wrote: >> On 05/16/2013 10:47 PM, Mark Nottingham wrote: >>> Note that this mechanism does not change the request message parsing >>> algorithm; in particular, whether or not a final response status code >>> is sent, the client still needs to send a complete request message. As >>> such, if a final status code is received, clients will often choose to >>> close the connection, rather than send a complete request (e.g., if it >>> is length-delimited). > > "the client needs to send a complete message" is perhaps too strong. > "the client needs to send a complete message if the client wants to keep > the connection open and the server response allows for a persistent > connection" may be more appropriate. Agreed. -- Mark Nottingham http://www.mnot.net/
Received on Tuesday, 28 May 2013 05:38:09 UTC