RFC 1122[0] says: A TCP connection may terminate in two ways: (1) the normal TCP close sequence using a FIN handshake, and (2) an "abort" in which one or more

RFC 1122[0] says: A TCP connection may terminate in two ways: (1) the normal TCP close sequence using a FIN handshake, and (2) an "abort" in which one or more RST segments are sent and the connection state is immediately discarded. and A host MAY implement a "half-duplex" TCP close sequence, so that an application that has called CLOSE cannot continue to read data from the connection. If such a host issues a CLOSE call while received data is still pending in TCP, or if new data is received after CLOSE is called, its TCP SHOULD send a RST to show that data was lost. So this behavior seems fine unless another RFC specifically prevents it. [0] - https://tools.ietf.org/html/rfc1122#section-4.2.2.13 https://tools.ietf.org/html/rfc1122#section-4.2.2.13