Using Fiddler with Localhost traffic
Fiddler is an indispensable web application development tool. For those who might not know what Fiddler is, it is a tool that allows you to see the complete request and response between your browser and the web server.
I am afraid that many developers may dismiss it as useless when they are trying to troubleshoot .Net development because it doesn’t show the traffic between the the web browser and the development web server that listens on localhost.
While this page has a few solutions to the problem. The solution can be solved easily by adding a period after “localhost” in your URL.
Instead of http://localhost:1234/MyApp/…,
use http://localhost.:1234/MyApp/… ( notice the extra dot after localhost).
sometimes the little changes make all the difference.
UPDATE: Another solution would be to use the Hostname of your machine instead of “localhost”.
If you found this page useful, consider linking to it.
Simply copy and paste the code below into your web site (Ctrl+C to copy)
It will look like this: Using Fiddler with Localhost traffic
Enjoy this post? Please consider leaving a comment or subscribe to the feed and get future articles delivered to your feed reader.
Comments
Jeff,
Thanks very much for this information adding the dot notation worked great! I am in the process of reverse engineering a large web app and read about Fiddler in a MSDN article. One of the senior developers here was using it so I decided to take the plunge this morning. What a fantastic tool, should be a standard part of any web developers toolkit.
Kind Regards,
Mark
[...] Another tool that can help in debugging web applications/services is Fiddler. Fiddler acts as a HTTP proxy, logging all HTTP traffic from the local computer to other computers. This however means that out-of-the-box HTTP debugging when using Cassini (i.e. the development web "server" in Visual Studio) is not possible. It has to be tweaked. [...]