Fiddler before Fiddler

I think origin stories are fun. I spoke about the origins of Fiddler in my talk at the PDC last year, and it was interesting to share how a little idea bloomed into a surprisingly widely-used piece of software. Cleaning up some old hard drives a few weeks ago, I found an old UI prototype that I’d been playing around with in 2002/2003. Like many of my early prototypes of that era, it was simply a piece of UI without any actual functionality. It made me smile however, so I’m going to publish it here for posterity:


Somewhat familiar perhaps, although I think some would have found the colors a bit jarring. 🙂 In case you’re wondering, “Bayden Systems” is the name I release most of my freeware under.

In other, more recent news, I’ll be doing another talk at the MiX Conference next month. This year’s talk is titled The Devil Went Down to HTTP: Debugging with Fiddler… it’s a play on a song title, in case you haven’t heard it. I have a few ideas for what I’ll be covering, but if you’ll be at MiX (or watching online) and have some suggestions for topics to cover or demos to do, please let me know!



Comments (3)

  1. Well, I guess the devil did go down to HTTP. Just look at the way how some ISPs are blocking every other IP protocol except HTTP and handful of others. (You won't realize it until one day, you decide to log into your company's Intranet over VPN, or remotely administer a computer over the Internet via Remote Desktop for Administration.) They do that because they know the risk of unnecessarily open ports… and the fact that probably no one objects their closing them.

    And all this because HTTP is becoming (but not yet quite there) the sole protocol used over the web.

  2. vadim kleyzit says:

    Fiddler is not just a widely-used piece of software. It is also a platform that hosts a number of useful extensions integrated into a powerful tool.  Fiddler’s extensible architecture inspires community-based efforts. Dozens of emerged add-ons made tasks such as security analysis, load testing, and code generating, simpler.  

    I think that more developers should know about Fiddler API such as IFiddlerExtension interface. How about adding a few minutes demo about creating a simple add-on to your talk?

  3. Chad says:

    Maybe having a set of ready-to-go examples of Fiddling with web pages and/or desktop apps that make web calls.  For instance, one of my favorite features of Fiddler is being able to AutoRespond.  I use a desktop app that frequently makes a web call to the affect of eventLog.php?blah=blah.  Well, I figured I could speed up the app by just locally auto-responding.  Sure enough, the app runs a little faster.  It's these types of capabilities that can appeal to more than just your developer needing to debug an app.

Skip to main content