Re: calculating page load up time using Wireshark

[Larry Rogers <kp4854 () outlook com>]

 Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.
 
Date: Fri, 14 Aug 2015 21:40:57 +0500
From: a.alii85 () gmail com
To: wireshark-users () wireshark org
Subject: Re: [Wireshark-users] calculating page load up time using Wireshark

So, this means with HTTP 1.1 its no longer stateless in that sense as browser does keep some form of "connection".

Laura in her WCNA , book mentioned the same technique, I have to find out which version of HTTP was her example written 
for.

I have workaround it like manually, as the wireshark is "ON" i keep a look on website page, as soon it loaded (which i 
check load-status icon at end of address bar) I close wireshark, then i see more accurate results.

But then I see that for complete page-load up perhaps the main index page is visible but at background there are other 
content e.g css,.theme files that are being downloaded from external sources (that are not visible on UI itself).

So, logically is it "ok" to close the wireshark as soon as the browser ended up loading the page. Thanks.

On Fri, Aug 14, 2015 at 7:34 PM, T B <phreakocious () gmail com> wrote:
This is going to be tricky, especially with HTTP 1.1 connections, as the browser could hold the connection open after 
the last element has been loaded.  It would be better to look for the last client ACK of a packet containing data, but 
I don't know of an easy way to get that level of specificity in a filter.  
On Fri, Aug 14, 2015 at 2:59 AM, asad <a.alii85 () gmail com> wrote:
Hello,

I'm using wireshark to calculate the page load up time for a website. I'm comparing the results from other online tools 
such as "http://www.webpagetest.org"; and see the results don't tally.

My capture filters is:

"dst host 1.1.1.1 or src host 1.1.1.1"

Further, my capture filter is 

"!(tcp.flags.reset == 1) && !(tcp.flags.fin == 1)"

I'm looking at page load up time through the following UI "statistics -> summary" and time between first and last 
packet.

Differences in coming in seconds not ms between online test and wireshark test done from my computer. I'm using 
wireless NIC card.

Is there a way to tweak the param's on wireshark to bring more close to real results.

regards
asad


___________________________________________________________________________

Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>

Archives:    https://www.wireshark.org/lists/wireshark-users

Unsubscribe: https://wireshark.org/mailman/options/wireshark-users

             mailto:wireshark-users-request () wireshark org?subject=unsubscribe



___________________________________________________________________________

Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>

Archives:    https://www.wireshark.org/lists/wireshark-users

Unsubscribe: https://wireshark.org/mailman/options/wireshark-users

             mailto:wireshark-users-request () wireshark org?subject=unsubscribe



___________________________________________________________________________
Sent via:    Wireshark-users mailing list 
Archives:    https://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request () wireshark org?subject=unsubscribe                                        

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request () wireshark org?subject=unsubscribe