by patrick.allen.higgins:

The http.Server struct contains ReadTimeout and WriteTimeout, but those are set right
after the connection is accepted and are not reset on subsequent requests on that
connection.

An http.Handler is not privy to the number of requests sent over a connection nor the
duration since the connection was created, so it cannot set the "Connection:
close" header based on this information.

Ideally, an idle-timeout on the connection could be established as well as read and
write deadlines for individual requests.

As it stands now, one must choose between these options:

1. keep-alives with a deadline which could mean the connection will be closed
mid-response, in violation of the recommendation in rfc2616 sec 8.1.4.

2. Disable keep-alive, which is undesirable with TLS.