To begin, let me say that this is an intermittent issue, and I'm not 100% sure it is caused by Fiddler.
I have an application that uses the IXMLHTTPRequest2 interface to make requests. I am trying to mock network requests using FiddlerCore.dll in my tests, but every so often I'm seeing the following behavior:
- I issue several requests, which succeed.
- I set up my IXMLHTTPRequest2 object and call Send(), which returns S_OK.
- Nothing happens for 20 seconds.
- Windows calls my OnError callback with E_FAIL.
I have added a BeforeRequest handler to FiddlerCore that logs every request seen (whether I end up mocking it out or not) and an OnLogString handler that simply passes through the logs to my test logger. The request doesn't show up anywhere. It seems to have disappeared without a trace somewhere between Windows and Fiddler.
I can't find any information about debugging issues with IXMLHTTPRequest2 on MSDN. Do you have any ideas about what may have happened, or where I can look to understand more?
Thanks,
Louis
2 Answers, 1 is accepted
Rank 1
No worries on the classification of the post-- I see them all and I answer most of them myself :-).
Having said that, do you ever have this problem with Fiddler itself (not FiddlerCore)? As Fiddler's proxy engine is fundamentally the same as FiddlerCore's, it would be revealing if you only saw this in a FiddlerCore-based application and not Fiddler itself.
Are you sending a large number of requests? Do you have a timeout set for the requests? Are the "missing" requests going to the same server as some earlier request, or to a different server? Are the "missing" requests using "POST" or another method that carries a request body?
If you could share the code you're using (send to fiddler @telerik.com), that could prove helpful.
Thanks!
Eric Lawrence
Telerik