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

Re: clarification of 7.2.2. Monitoring Connections for Error Status Messages

From: Mark Nottingham <mnot@mnot.net>
Date: Mon, 19 Apr 2010 22:52:48 +1000
Cc: Wenbo Zhu <wenboz@google.com>, ietf-http-wg@w3.org
Message-Id: <5287F299-C39A-48E8-908D-B91FBD602A3C@mnot.net>
To: Jamie Lokier <jamie@shareable.org>
No; I think we're saying the same thing; that HTTP servers can't* violate the linear nature of time, in that if they choose to send the response before getting the full request, there are still things they don't know about that request. 

Cheers,


* lacking a madman with a blue box, of course.


On 19/04/2010, at 10:36 PM, Jamie Lokier wrote:

> Mark Nottingham wrote:
>> Well, it has to live with the consequences of sending that status line -- including the possibility that the request is malformed, incomplete, etc.
> 
> Ah, but according to the spec, that should not be a consequence.
> 
> If you send an "error status" an incomplete request is to be expected.
> The server shouldn't rely on getting the whole request.
> 
> But if you send a non-error status, the spec doesn't suggest the
> client truncates the request - no more than normal anyway.  So the
> server should be able to depend on getting the request just as much as
> if it hadn't sent the status yet (barring client implementation quirks).
> 
> Are you saying the spec is incomplete in this regard?
> 
> -- Jamie


--
Mark Nottingham     http://www.mnot.net/
Received on Monday, 19 April 2010 12:53:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:18 GMT