Keep - the alive and the timeout setting 100 milliseconds, for example, the client sends multiple requests actually is to use the same socket connection, trying to figure out the connection of the close process
Problem of 1:100 milliseconds comes, if the client did not take the initiative to close connection (connection: close), the server will be how to deal with? Will take the initiative to send the client connection: close to confirm the command or directly when closing the socket channel subsequent messages will no longer deal with?
Question 2: in 100 milliseconds, the client socket on this new request, and a message when you arrive at the server has passed 100 mm, the service side is how to deal with it?

I watch the official documentation HTTP seems also not too clearly shows that the process of baidu did not
https://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html#sec8
I hope the great spirit guide! Speak clearly

CodePudding user response:

The above problem a is equal to: http1.1 after the connection is established, the client suddenly hang up and the server will be how to deal with the connection, is closed for sure, how close?
Such as the timeout directly closed after 100 milliseconds? First and client confirmed that received confirmation close again? Has received confirmation reply to wait for a period of time after shut down again?

If send confirm question 2 is equal to: send confirmation but haven't received reply, among this received a new request, the client the request is how to dispose of?

You ever think that online will have the possibility that this kind of situation! So I want to learn