| Bug ID |
10283
|
| Summary |
Decoding websocket protocol client side very large message flags an error when there is none
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.8.10
|
| Hardware |
x86-64
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Capture file support (libwiretap)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 12900 [details]
Compressed pcap file
Build Information:
Version 1.10.8 (v1.10.8-2-g52a5244 from master-1.10)
Copyright 1998-2014 Gerald Combs <[email protected]> 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.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, without Kerberos, with GeoIP, with
PortAudio V19-devel (built Jun 12 2014), with AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.
Intel(R) Core(TM) i7-4702HQ CPU @ 2.20GHz, with 16287MB of physical memory.
Built using Microsoft Visual C++ 10.0 build 40219
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
I have a _javascript_ client that sends MQTT messages over Websocket.
I captured packets on port 8001 while doing the following:
- Making a WebSocket connection
- Sending a large message, 124,000 bytes
- Receiving the same large message back (pub/sub)
- Disconnect
All worked as expected. The message was received intact. However while browsing
the pcap file, I noticed Wireshark flags the outbound WebSocket message with
the very large message (stream) as MALFORMED. Such is not the case. I was
testing a pub/sub client which gets back from the server the very large
message. The server in question (back end) was Apache MQ 5.10.0.
I enclose the pcap file along with the text message used to test.
Regards,
Dan Smith
KAAZING
You are receiving this mail because:
- You are watching all bug changes.
