Scott Lawrence wrote:
> But closing the connection is perfectly acceptable under these
> circumstances; there is no reason why the server should continue to
> receive the data if that creates a server problem. The server can
> generate the error response and close the connection.
The problem with this method is that some clients end won't be able to
read the response; as soon as the connection is closed and the client
tries to write to the socket, it will get an error back and won't be
able to read the error response from it.
This isn't an issue if the client checks for incoming messages before
it writes the next block of data, however many clients do not (nor is
it required by HTTP/1.1). If the client software considers a broken
connection as a server going down (instead of an error), then it may
continue trying to send the document, further tying up the server...
Michael Sweet, Easy Software Products mike at easysw.com
Printing Software for UNIX http://www.easysw.com