| Bug ID |
12247
|
| Summary |
GUI not showing the HTTP requests propery
|
| Product |
Wireshark
|
| Version |
2.0.2
|
| Hardware |
x86
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 14409 [details]
capture
Build Information:
Version 2.0.2 (v2.0.2-0-ga16e22e from master-2.0)
Copyright 1998-2016 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 Qt 5.3.2, with WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale C, with
WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version
1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.2.15, with Gcrypt 1.6.2, without
AirPcap.
Intel(R) Core(TM) i7-3740QM CPU @ 2.70GHz (with SSE4.2), with 24142MB of
physical memory.
Built using Microsoft Visual C++ 12.0 build 40629
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
The GUI doesn't display properly the requests in the attached capture. For
example follow the TCP stream starting with packet 17 - the GUI shows only the
first request and even this one is wrongly parsed because the data from this
POST request is missing (well, it is there as packet 27 but this packet 27 is
not linked to packet 23 which holds the HTTP header). The rest of the requests
in this session are simply not displayed.
The weird thing is that if I extract only this session in a separate pcap file
and load it, everything looks fine in the GUI.
The same problem exists in all 4 complete TCP sessions in this capture. Because
of this issue other filters like "http.request" for example show wrong output.
You are receiving this mail because:
- You are watching all bug changes.