Wireshark-bugs: [Wireshark-bugs] [Bug 2883] New: Timing of packets in a mess
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 17 Sep 2008 22:44:17 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2883

           Summary: Timing of packets in a mess
           Product: Wireshark
           Version: 1.1.x (Experimental)
          Platform: Macintosh
        OS/Version: Mac OS X 10.5
            Status: NEW
          Severity: Major
          Priority: Medium
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: tc1024@xxxxxxxx


Build Information:
Wireshark 1.1.1-SVN-26226 Intel.dmg
--
Compiled with GTK+ 2.12.9, with GLib 2.16.3, with libpcap 0.9.5, with libz
1.2.3, without POSIX capabilities, without libpcre, without SMI, without
c-ares,
without ADNS, without Lua, without GnuTLS, without Gcrypt, with MIT Kerberos,
without PortAudio, without AirPcap.
--
No matter the stable or lastest snapshot version is used, there is a timing bug
in packets :
consider HTTP (www.bbc.co.uk) : i browse / then i get the page that asks me to
download some other elements like image or javascript or css, right ?

The problem is that wireshark decodes :
No | TIME   | Info
11 | 9.465 | GET / HTTP/1.1
47 | 9.767 | GET /home/release-19-2/script/glow.homepage.compressed2.js
HTTP/1.1
49 | 9.813 | HTTP/1.1 304 Not Modified
91 | 9.879 | HTTP/1.1 200 OK (text/html)

So please how could you explain that my browser now where to fetch the js
before he got the answer of the page ? So there is a timing bug in the
decoding. Check it yourself, i think you can easily reproduce this by browsing
some site (here www.bbc.co.uk) with a modern navigator and filtering only http
traffic.


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