94 + 181 = 275 that means there are another 181 bytes in that packet which may be TCP options but these are normally limited to 40 bytes. While "zero-length" TCP packets have 94 bytes of eth + ip + tcp overhead, the GET has total length of 456 bytes and the ACK to it says 181 bytes of payload have been received in it. In your case, it is hard to say whether the receiving side (the http server) acknowledges the whole http GET packet or only a part of it, because we cannot click to another packet and see what is inside on a screenshot. about successful reception of data or, vice versa, about missing data which need to be retransmitted. the other party has sent something which prevents the first one from responding,īecause something is wrong with that party's application itself.Ī "zero-length" TCP packet merely means that the party sending it had no payload to send but needed to inform the other one about something, e.g. But the question "why has it stopped responding" may have two answers:īecause something was wrong at protocol level, i.e.
Wireshark can help you answer the question "why" only in terms that it shows you which party in communication has stopped responding at a given layer.
0 kommentar(er)
