Conformant HTTP 1.1 Server and client-side connection half-close

I've observed a HTTP 1.1 Server implementation, which terminates a client connection as soon as it detects a client-side connection shutdown of its outgoing channel (or rather, either before or after sending a proper http response). Is this a conforming HTTP 1.1 implementation?

RFC 2616 Section 8.1.4 seems to suggest this is to be the proper behaviour:

When a client or server wishes to time-out it SHOULD issue a graceful close on the transport connection. Clients and servers S开发者_开发知识库HOULD both constantly watch for the other side of the transport close, and respond to it as appropriate.

...

Servers SHOULD NOT close a connection in the middle of transmitting a response, unless a network or client failure is suspected.

Am I interpreting it right? Is there a more explicit reference about half-closed connection handling in the context of HTTP 1.1?

---

As far as i know, thats is all we need to know about Half-closed connections.

The server will only close the connection if it detects that the client closed it (it can ben when the server is about to write to the socket) or at the end of the request, if it does not support connection: keep-alive.

The client can disconnect any time, but it should tell the server why is it disconnecting (time_out, request cancel). But it is not very used by those who write sockets components. They just close the socket when they need to force a time_out.

But the client implementation is not the problem. You should worry about server implementation since suffer a lot with those unexpected disconnects.

EDIT

Maybe those links can help you.

Transmission Control Protocol - Functional Specification

TRANSMISSION CONTROL PROTOCOL