Wireshark interprets websocket frames after HTTP handshake in a wrong way
This issue was migrated from bug 16274 in our old bug tracker.
Original bug information:
Reporter: jf…@skc…
Status: RESOLVED FIXED
Product: Wireshark
Component: Dissection engine (libwireshark)
OS: Windows 10
Platform: x86-64
Version: 3.0.7
Attachments:
: what wireshark thinks is the websocket frame but its not
websocketbug.pcapng: websocket text message misinterpreted as pong frames