How to configure Fiddler to listen to localhost?

LocalhostFiddler

Localhost Problem Overview


I want to monitor HTTP traffic between a process on my local machine and another (server) process, also running on my local machine.

How can I configure Fiddler to listen to traffic to and from localhost?

Localhost Solutions


Solution 1 - Localhost

By simply adding fiddler to the url

http://localhost.fiddler:8081/

Traffic is routed through fiddler and therefore being displayed on fiddler.

Solution 2 - Localhost

Add a dot . after the localhost.

For example if you had http://localhost:24448/HomePage.aspx

Change it to http://localhost.:24448/HomePage.aspx

Internet Explorer is bypassing the proxy server for "localhost". With the dot, the "localhost" check in the domain name fails.

Solution 3 - Localhost

.NET and Internet Explorer don't send requests for localhost through any proxies, so they don't come up on Fiddler.

Many alternatives are available

Use your machine name instead of localhost. Using Firefox (with the fiddler add-on installed) to make the request. Use http://ipv4.fiddler instead of localhost.

For more info http://www.fiddler2.com/Fiddler/help/hookup.asp

Solution 4 - Localhost

try putting your machine name/IP address instead of 'localhost' into URL. Works for me...

Solution 5 - Localhost

Rather than configure the application server and client to use another domain, you may want to configure the client application to use a proxy. Fiddler also creates a proxy you can use, logging all traffic. Rick Strahl blogged about using this in .NET Apps, I am always misplacing this blog post, so let me link it here: http://weblog.west-wind.com/posts/2008/Mar/14/Debugging-Http-or-Web-Services-Calls-from-ASPNET-with-Fiddler.

To be brief, the app.config change is:

<system.net>
  <defaultProxy>
    <proxy  proxyaddress="http://127.0.0.1:8888" />      
  </defaultProxy>
</system.net>

Solution 6 - Localhost

You cannot. Instead if you machine is named "myMachine", point your browser to http://mymachine instead of http://localhost

Solution 7 - Localhost

And I just found out that on vista 'localhost.' will not work. In this case use '127.0.0.1.' (loopback address with a dot appended to it).

Solution 8 - Localhost

tools => fiddler options => connections there is a textarea with stuff to jump, delete LH from there

Solution 9 - Localhost

Replace localhost by lvh.me in your URL

For example if you had http://localhost:24448/HomePage.aspx

Change it to http://lvh.me:24448/HomePage.aspx

Solution 10 - Localhost

Replace localhost with 127.0.0.1 If it doesn't work change the run configuration to support your ip address.

Solution 11 - Localhost

I am running Fiddler v4.4.7.1. I needed to use localhost:8888 or machinename:8888 when using the Composer tab. Look at the Help/About Fiddler menu option, where it says, "Running on:". Mine shows machinename:8888 there.

Solution 12 - Localhost

The Light,

You can configure the process acting as the client to use fiddler as a proxy.

Fiddler sets itself up as a proxy conveniently on 127.0.0.1:8888, and by default overrides the system settings under Internet Options in the Control Panel (if you've configured any) such that all traffic from the common protocols (http, https, and ftp) goes to 127.0.0.1:8888 before leaving your machine.

Now these protocols are often from common processes such as browsers, and so are easily picked up by fiddler. However, in your case, the process initiating the requests is probably not a browser, but one for a programming language like php.exe, or java.exe, or whatever language you are using.

If, say, you're using php, you can leverage curl. Ensure that the curl module is enabled, and then right before your code that invokes the request, include:

curl_setopt($ch, CURLOPT_PROXY, '127.0.0.1:8888');

Hope this helps. You can also always lookup stuff like so from the fiddler documentation for a basis for you to build upon e.g. http://docs.telerik.com/fiddler/Configure-Fiddler/Tasks/ConfigurePHPcURL

Solution 13 - Localhost

If you're using FireFox, Fiddler's add-on will automatically configure it to not ignore localhost when capturing traffic. If traffic from localhost is still (or suddenly) not appearing, try disabling and re-enabling traffic capture from Fiddler to goad the add-on into fixing the proxy configuration.

Solution 14 - Localhost

This is easy. Just grab your computer's IP address with IPconfig at the command prompt. Then, hit the service using the IP address rather than localhost. You don't need to do anything to Fiddler to make this work, it will just work by itself.

Solution 15 - Localhost

Specific to Firefox, which does not go through Internet Options like IE, Chrome, and Edge do, you can use about:config to modify preferences, find the preference network.proxy.no_proxies_on and remove localhost from it.

This was the default setting for Firefox Developer Edition 66.0b2 and worked with Fiddler 5.0.20182.28034.

(Other listed solutions do work, this solution allows you to not change the host you are navigating to.)

Solution 16 - Localhost

Go to proxy settings in Firefox and choose "Use system proxy" but be sure to check if there is no exception for localhost in "no proxy for" field.

enter image description here enter image description here

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionThe LightView Question on Stackoverflow
Solution 1 - LocalhostTomerView Answer on Stackoverflow
Solution 2 - LocalhostOleg GrishkoView Answer on Stackoverflow
Solution 3 - LocalhostjatinView Answer on Stackoverflow
Solution 4 - LocalhostmyroView Answer on Stackoverflow
Solution 5 - LocalhostFrank SchwietermanView Answer on Stackoverflow
Solution 6 - LocalhostAliostadView Answer on Stackoverflow
Solution 7 - LocalhostMichal B.View Answer on Stackoverflow
Solution 8 - LocalhostbresleveloperView Answer on Stackoverflow
Solution 9 - LocalhostHosseinView Answer on Stackoverflow
Solution 10 - Localhostuser2357935View Answer on Stackoverflow
Solution 11 - LocalhostpollifaxView Answer on Stackoverflow
Solution 12 - LocalhostpaulatumwineView Answer on Stackoverflow
Solution 13 - LocalhostSuncat2000View Answer on Stackoverflow
Solution 14 - LocalhostChristian FindlayView Answer on Stackoverflow
Solution 15 - LocalhostmlhDevView Answer on Stackoverflow
Solution 16 - LocalhostMariusz PawelskiView Answer on Stackoverflow