About Wireshark and http/tcp stream -
anyone can tell me why received http 200 response before send request? weird.
actually request sent in packet #747. can catch following facts:
- the size of packet (628 bytes) - it's enough send
- the response received server.
this request doesn't have body has content-type
header. guess because of header wireshark thinks it's going body , tries wait until packet #776. i've checked similar scenario without content-type
header , wireshark displays request in right place.
rfc says "the presence of message-body in request signaled inclusion of content-length or transfer-encoding header field in request's message-headers." there should not body. know wireshark serves working not standard or well-implemented variants of protocols. think not bug.
Comments
Post a Comment