Re: Long delay between ClientConnected and ClientBeginRequest / ClientBeginRequest and ServerGotRequest

[EricLaw]

A long delay between ClientConnected and ClientBeginRequest typically means that the request you're looking at is the 2nd (or later) on a given client connection; the client has reused the connection to send more than one request. If this was the first request from the client, this would typically indicate a bug in the client, but that's not common.

 

A long delay between FiddlerBeginRequest and ServerGotRequest typically indicates that the request took a long time to send from the client to the server (e.g. because it was a large upload). It's also possible to see a long time here if for some reason the server connection failed and the client had to attempt to resend the request on a new connection.

 

A long delay between ServerConnected and FiddlerBeginRequest typically means that the request you're looking at is the 2nd (or later) on a given server connection; Fiddler has reused the connection to send more than one request. If this was the first request from Fiddler, this would typically indicate a bug in Fiddler (or you have a breakpoint or other latency set).

On Wednesday, October 31, 2012 9:52:05 PM UTC-5, Matthew Pickle wrote:

Could someone tell me what the times between the following timers signify?

 

• ClientConnected and ClientBeginRequest
• ClientBeginRequest and ServerGotRequest

ClientConnected: 22:42:54.641
ClientBeginRequest: 22:42:56.220
GotRequestHeaders: 22:42:56.220
ClientDoneRequest: 22:43:00.204
Determine Gateway: 15ms
DNS Lookup:   0ms
TCP/IP Connect: 0ms
HTTPS Handshake: 0ms
ServerConnected: 22:42:54.063
FiddlerBeginRequest: 22:43:00.220
ServerGotRequest: 22:43:00.220
ServerBeginResponse: 22:43:00.251
GotResponseHeaders: 22:43:00.251
ServerDoneResponse: 22:43:00.251
ClientBeginResponse: 22:43:00.251
ClientDoneResponse: 22:43:00.251