When I initialize TCP connection and send data, my application (client) delays for 30 seconds. Via Wireshark I see that response body is already received (15,16 packets), however the app waits for FIN packet from server (17 packet).
Packets snapshot via wireshark: https://www.dropbox.com/s/il8zkik5w88...
How can I shrink the delay?
The answer is, it is application related. Normally the client initialized a session and he also ends a session. As he is the only one who knows, if he wants more data from the server or not. But in your case the client does not close the session. So the servers ends the session nicely by sending a fin packets after 30 seconds. So from my point of view, the question should be, why does the client not close the session itself.
Asked: 2017-11-01 05:11:02 +0000
Seen: 1,027 times
Last updated: Nov 01 '17
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
@Nurlan: I have reopened the question again. As accepting the answer which solved the question is enough. Closing is not necessary.