Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 7537] New: Statistics > HTTP > Packet Counter shows wrong

Date: Fri, 27 Jul 2012 09:34:52 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7537

           Summary: Statistics > HTTP > Packet Counter shows wrong count
           Product: Wireshark
           Version: 1.9.x (Experimental)
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Low
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: Jim@xxxxxxxxxxxxxxxxx


Created attachment 8848
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=8848
Web browsing session to www.wiresharkbook.com

Build Information:
Version 1.9.0-SVN-44057 (SVN Rev 44057 from /trunk)

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 (32-bit) with GTK+ 2.24.10, with Cairo 1.10.2, with Pango 1.30.0, with
GLib 2.32.2, with WinPcap (4_1_2), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Jul 26 2012), with AirPcap.

Running on Windows XP Service Pack 3, build 2600, 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.12.18, Gcrypt 1.4.6, without AirPcap,  from the
PortableApps U3 device in drive E:.

Built using Microsoft Visual C++ 10.0 build 40219

--
Statistics > HTTP > Packet Counter is not correctly identifying and counting
all "200 OK" responses.

TO RE-CREATE:

Download the attached file, which is a browsing session to
www.wiresharkbook.com. Go to Statistics > HTTP > Packet Counter. It will show
12 GET requests and 8 responses, all of which are "200 OK" responses.

Now apply the display filter "http.response.code == 200". It will show that
that there are 12 "200 OK" responses. The same thing will be seen by going to
Expert Infos > Chats: 12 "200 OK" responses.

The same thing can also be seen in the trace file http-cnn20111.pcapng,
available from the download section of www.wiresharkbook.com. Statistics > HTTP
> Packet counter shows 132 "200 OK" responses. Applying the
"http.response.code==200" display filter, or going to Expert Infos > Chats,
shows 136 "200 OK" responses.

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