Announcing the Fiddler Blog

Welcome to the new Fiddler blog on MSDN! I'm Eric, developer of the Fiddler Web Debugger.

While I occasionally would blog Fiddler news over on BlogSpot, I didn't do so very often, and certainly not in the depth that I provide in my other MSDN blog, IEInternals. So I've started this blog so I'll have a place to talk about:

  • New versions of Fiddler and FiddlerCore
  • Fiddler Add-ons and Extensions
  • Any books / talks / articles that relate to Fiddler 
  • Interesting things being created by the Fiddler community
  • Miscellaneous .NET things I've learned while writing Fiddler
  • Web debugging in general
  • Anything else that comes up 🙂

So, thanks for reading... I hope you'll find this blog a valuable source of information. If you have any suggestions for what you'd like to hear more about, please let me know!

-Eric Lawrence

Comments (4)

  1. JimMarschik says:

    Thanks Eric- looking forward to checking up on this!

  2. Sunny says:

    Hi Eric,

    I do not know whether this is the right place where I can post my question. But I have a query regarding the response time measurement done through nexpert.

    I measure the response time for a particular transactions using a stopwatch and using Nexpert. There is huge difference between the two. After many repetitions, visibly I find that the timing measured by stopwatch are correct and that by Nexpert are very high. Please advice how I can resolve this issue.



  3. Hey Sunny,

    The timing in nexpert are pulled directly from Fiddler.  If you check the timeline view in Fiddler are you seeing long response times as well?

    Also, the timings are based on where you place your step marker.  If you place it on the wrong object, the timings could be thrown off.

    If you dont mind emailing your answers/SAZ file to I can take a look for you.


    Eric Mattingly

  4. Sunny says:

    Hi Eric, I have e-mailed the SAZ files. Please have a look at it and reply to the e-mail. Regards, Sunny

Skip to main content