Scott Cate's WebLog

You just don't know what
you don't know.

community

frenz

my book(s)

my products

Working with Fiddler on LocalHost

Developing ASP.NET AJAX (or any AJAX really) is tremendously easier if you can watch the traffic going across the wire. There are a lot of ways to accomplish this, but I think Fiddler is the most popular Windows application for ASP.NET developers. Sure there is Firebug, and probably a million others, but this post is about Fiddler).

Over the last few years, I've had a hard time getting Fiddler to work on local host. Actually until recently, it's just never worked.

Rumors online said to use http://127.0.0.1, instead of http://localhost and it'll work. Maybe for you, but not for me.

Then last month while speaking at Orlando ASPConnections, I was demoing some AJAX calls on stage, and an audience member told me that Fiddler will work on 127.0.0.1 with a trailing . on the IP address. So the address ends up like ...

Or

With a port number (if you're on Cassini).

Fiddler picks up this traffic and you're back in control of sniffing your own traffic.

Hope this helps others that didn't know the little nugget.

Comments

Denny.NET said:

Debug on LocalHost with Fiddler

# May 22, 2008 4:08 PM

Josh Schwartzberg said:

You can also use your computer name.

# May 22, 2008 5:33 PM

timheuer said:

webdevhelper rocks the house in my opinion compared to fiddler for this type of dev.  and it has a json visualizer for ajx data dev...

# May 22, 2008 7:14 PM

Guy Ellis said:

Thanks Scott - I recall having this problem in the past and never finding a solution to it.

# May 23, 2008 2:58 PM

links for 2008-05-23 « dstelow notes… said:

Pingback from  links for 2008-05-23 « dstelow notes…

# May 23, 2008 7:35 PM

Christopher Steen said:

Sharepoint Moving a sharepoint workflow between solutions - “Failed on Start (retrying)” [Via: Greg...

# May 24, 2008 6:38 AM

Christopher Steen said:

Link Listing - May 23, 2008

# May 24, 2008 6:38 AM

DotNetKicks.com said:

You've been kicked (a good thing) - Trackback from DotNetKicks.com

# July 4, 2008 12:04 AM

docluv said:

http://localost./ works, not sure why exactly, but it makes it work. Also you need to turn off IP6 compatability.

http://localhost.:5555/ for the development web server.

# July 4, 2008 6:29 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)