Boost::asio fails to close TCP connection cleanly?

The server should not close the socket. If the server closes the socket and the client sends more data or there is data in the receive queue then the client will receive a RST causing this error. See cs.baylor.edu/~donahoo/practical/CSocket....

The server should not close the socket. If the server closes the socket and the client sends more data or there is data in the receive queue then the client will receive a RST causing this error. See cs.baylor.edu/~donahoo/practical/CSocket... The HTTP server should read the entire client request or in the case of HTTP/1.1 the entire sequence of client requests.In this example it does not read any of the client request so there is data in the receive queue, so that the client receives a reset.

Drain the socket with a sequences of async_reads before closing - probably in the future you will want to actually parse the client request ;-).

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.