Wireshark-bugs: [Wireshark-bugs] [Bug 4727] New: The HTTP dissector can not resemble correctly o
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 29 Apr 2010 08:09:52 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4727

           Summary: The HTTP dissector can not resemble correctly out of
                    order segments in Wireshark GUI when the first
                    captured packet is not the first packet from the
                    request
           Product: Wireshark
           Version: 1.2.7
          Platform: Other
        OS/Version: Windows 7
            Status: NEW
          Severity: Normal
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: milkovm@xxxxxxxxxxx


Build Information:
Version 1.2.7 (SVN Rev 32341)

Copyright 1998-2010 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 with GTK+ 2.16.6, with GLib 2.22.4, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, without libpcre, with SMI 0.4.8,
with c-ares 1.7.0, with Lua 5.1, with GnuTLS 2.8.5, with Gcrypt 1.4.5, with MIT
Kerberos, with GeoIP, with PortAudio V19-devel (built Mar 31 2010), with
AirPcap.

Running on 32-bit Windows 7, build 7600, with WinPcap version 4.1.1 (packet.dll
version 4.1.0.1753), based on libpcap version 1.0 branch 1_0_rel0b (20091008),
GnuTLS 2.8.5, Gcrypt 1.4.5, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 30729

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 HTTP dissector can not resemble correctly out of order segments in the
Wireshark GUI when the first captured packet is not the first packet from the
request. Please look at the attached capture. It consists of single TCP stream.
If you look at packets 32 and 34. They represent one POST request from the
client but they arrived out of order - first the second packet (packet 32) and
then the first packet (packet 34). the GUI does not show the POST request. You
can see multiple similar problems throughout this TCP session - for example
packets 235 and 237, 361 and 363, 387 and 389, etc.

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