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

Well, it has to live with the consequences of sending that status line -- including the possibility that the request is malformed, incomplete, etc.

Many people have asked for a way for a server to change the status code, etc. once the status line has been sent (e.g., because they've encountered an error during streaming). AFAIK the only practical way to indicate a problem in HTTP (i.e., not in the body) is to make the response incomplete (usually by dropping the connection); while you could indicate something in trailers, not many people are able to or bother to check them.


On 19/04/2010, at 11:31 AM, Jamie Lokier wrote:

> Mark Nottingham wrote:
>> The server isn't required to wait for the entire request before sending a status. Is that what you're looking for?
> Ah, but is the server allowed to depend on receiving the remainder of
> the request after it has sent a non-error status?
> Section 7.2.2 talks about the client aborting the request body only in
> the cases of an "error status".
> -- Jamie

Mark Nottingham

Received on Monday, 19 April 2010 05:11:26 UTC