I have a single TCP flow in a pcap. "Follow --> TCP Stream" seems to be showing the wrong HTTP payload in Wireshark 2.2.1 (Win7-64 SP1). (But all 23 packets seem to be shown correctly; it's just the payload decode that seems to be incorrect.) Is this a known bug? I searched but didn't find an existing defect. Anyone else observed something similar? Note, "Follow --> TCP Stream" does seem to work correctly in Wireshark 2.0.1 (Mac OSX 10.11.6). asked 17 Oct '16, 09:17 wwwalker edited 17 Oct '16, 09:23 |
One Answer:
Looks like you're running into bug 12855. answered 17 Oct '16, 12:30 JeffMorriss ♦ |