This value is controlled by the preference: fiddler.network.timeouts.serverpipe.receive.initial By default, its value is -1, which means it relies on .NET/Windows to use whatever timeout it uses for "infinite". You can set a specific value by providing a number of milliseconds (e.g. 60000 for one minute). |
/*
// This function executes just before Fiddler returns an error that it has
// itself generated (e.g. "DNS Lookup failure") to the client application.
// These responses will not run through the OnBeforeResponse function above.
static function OnReturningError(oSession: Session) {
}
*/
I'm running Fiddler to watch some traffic and from time to time I get 504 from Fiddler.The response has following header:===============================================================================HTTP/1.1 504 Fiddler - Receive FailureContent-Type: text/html; charset=UTF-8
Connection: close
Timestamp: 10:08:36.697[Fiddler] ReadResponse() failed: The server did not return a response for this request.===============================================================================This seems to happen randomly, the session has a "green down arrow" icon which according to Fiddler's website indicates "Response is being read from the server" and after 5 mintues or 5 minutes and some seconds it turns to 504 and returns the headers shown above.As I understand it the problem is that the remote server did not return a response in 5 minutes which seems to be some sort of a hardcoded timeout in Fiddler.However what bugs me most is that I can't handle this situation in OnBeforeResponse where I have following code:...if (oSession.responseCode == 504) {
MessageBox.Show("Got 504");}It seems like with 504 OnBeforeResponse is skipped.If you have any ideas on how to track down the cause of this 504 and maybe do a reply when they happen I'd be really grateful.Cheers,Pete.