Wireshark-bugs: [Wireshark-bugs] [Bug 6843] New: Decoding Websocket protocol (RFC6455)
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 14 Feb 2012 21:32:35 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6843

           Summary: Decoding Websocket protocol (RFC6455)
           Product: Wireshark
           Version: 1.6.5
          Platform: x86
        OS/Version: Windows 7
            Status: NEW
          Severity: Enhancement
          Priority: Low
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: simon@xxxxxxxxxxxxxxxx


Build Information:
Version 1.6.5 (SVN Rev 40429 from /trunk-1.6)

Copyright 1998-2012 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with GTK+ 2.22.1, with GLib 2.26.1, with WinPcap (version
unknown), with libz 1.2.5, without POSIX capabilities, without libpcre, without
SMI, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.10.3, with
Gcrypt 1.4.6, without Kerberos, with GeoIP, with PortAudio V19-devel (built Jan
10 2012), with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.10.3, Gcrypt 1.4.6, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 21022
--
At present it appears that WireShark does not support the decoding the
websockets (RFC6455) protocol.

Everything is ok up until (and including) the switching protocol packet.  After
this data messages are exchanged, but WireShark cannot decode them correctly
and they appear as a [Malformed Packet].

While this is a new protocol that has been changing quite a bit over the last
year it appears that it may be becoming stable.  So far Chrome is the only
browser that has support for RFC6455, but FF11 (due mid march) is also supposed
to be including it.  I also believe IE10 is meant to have support (whenever it
gets released).

Cheers
Simon

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.