For HTTP requests that have KeepAlive indicated in the response header, the internal connection is not closed so that a subsequent request may continue using the existing connection. However, when the client application aborts in the middle of receiving the response, the connection must be closed to avoid being left in an invalid state (where the some of the remainder of the aborted request may have already been received and would incorrectly be read as the first bytes of the nexxt response). The internal fix was to always close the connection after an abort so that the next HTTP operation starts afresh on a new connection.