ClientConnected versus ClientBeginRequest

[Bill]

I have analyzed a Fiddler log and saw strange times for
ClientConnected and ClientBeginRequest.

On some log entries the difference between ClientConnected and
ClientBeginRequest are multiple seconds while the majority of the log
entries have small deltas between these two times.

Example:
ClientConnected: 09:50:31.066
ClientBeginRequest: 09:50:41.113

The delta is almost 10 seconds between the above times.

For the same exact web page there are other log entries where the
ClientConnected and ClientBeginRequest are exactly the same.

Questions:
Is ClientConnected the time the client clicked "Submit"?
Where could this time be accumulating?

The client java script is exactly the same for this page; so would the
time be in network?

Thanks
Bill

[EricLaw]

That's entirely expected in cases where the client's request was sent
on a reused client socket. ClientConnected refers to the connection
time of the socket connection from the browser to Fiddler. Because
those socket connections may be reused, you can often see cases where
ClientConnected is even minutes earlier than ClientBeginRequest,
because the socket was originally connected for, say, request #1, and
then later reused for, say, request #12 a few seconds later, then
request #20 about 20 seconds later, and later request #35 nearly a
minute later, etc.

By default, a client socket is kept alive if it is reused within 30
seconds (pref named
"fiddler.network.timeouts.clientpipe.receive.reuse") of the previous
request.

[Bill]

Then ClientBeginRequest/ClientEndResponse is the correct time to use
to calculate response time.

ClientBeginRequest is when the form is "submitted" and after any java
script that is executed before submit.

Thanks
Bill

> > Bill- Hide quoted text -
>
> - Show quoted text -