https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15017
Peter Wu <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|UNCONFIRMED |RESOLVED
CC| |[email protected]
See Also| |https://bugs.wireshark.org/
| |bugzilla/show_bug.cgi?id=13
| |523
--- Comment #1 from Peter Wu <[email protected]> ---
The Follow TCP Stream interpretation is correct, Follow HTTP shows the wrong
data due to a defect in TCP reassembly. The root cause is the same as bug 13523
and its related issues, so I am marking it as duplicate. The problematic part:
- frame 4 has seq=2, len=43
- frame 6 has seq=1, len=44
Possible interpretation:
(lost segment: seq=1, len=1)
Frame 4 (seq=2, len=43) is received (but not ACKed).
Frame 5 (seq=1, len=44) covers the previous two segments (retransmission).
*** This bug has been marked as a duplicate of bug 13523 ***
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <[email protected]>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:[email protected]?subject=unsubscribe
