How do I get Fiddler to stop ignoring traffic to localhost?

LocalhostFiddler

Localhost Problem Overview


When using Fiddler to monitor HTTP Requests & Responses in Internet Explorer it ignores all traffic directed to http://localhost.

Localhost Solutions


Solution 1 - Localhost

To get Fiddler to capture traffic when you are debugging on local host, after you hit F5 to begin degugging change the address so that localhost has a "." after it.

For instance, you start debugging and the you have the following URL in the Address bar:

http://localhost:49573/Default.aspx

Change it to:

http://localhost.:49573/Default.aspx

Hit enter and Fidder will start picking up your traffic.

Solution 2 - Localhost

Fiddler's website addresses this question directly.

There are several suggested workarounds, but the most straightforward is simply to use the machine name rather than "localhost" or "127.0.0.1":

http://machinename/mytestpage.aspx

Solution 3 - Localhost

The correct answer is that it's not that Fiddler ignores traffic targeted at Localhost, but rather that most applications are hardcoded to bypass proxies (of which Fiddler is one) for requests targeted to localhost.

Hence, the various workarounds available: http://fiddler2.com/documentation/Configure-Fiddler/Tasks/MonitorLocalTraffic

Solution 4 - Localhost

Fiddler v4.5.1.0 will allow you to go to replace "localhost" with "localhost.fiddler", and present localhost as the host name for the receiving server running on your machine.

This avoids "host not recognised" errors when connecting to WCF services with the built in web server that visual studio uses.

i.e. Instead of http://localhost:51900/service.wcf you can use http://localhost.fiddler:51900/service.wcf

Solution 5 - Localhost

Internet Explorer has a new feature since IE9 RC: adding <-loopback> to the proxy bypass list causes WinInet (the network library used by IE) to send requests destined for localhost and 127.0.0.1 through the defined proxy.

Here's the original announcement by @EricLaw: http://blogs.msdn.com/b/fiddler/archive/2011/02/10/fiddler-is-better-with-internet-explorer-9.aspx

Solution 6 - Localhost

For Fiddler to capture traffic from localhost on local IIS, there are 3 steps (It worked on my computer):

  1. Click Tools > Fiddler Options. Ensure Allow remote clients to connect is checked. Close Fiddler.

enter image description here

  1. Create a new DWORD named ReverseProxyForPort inside KEY_CURRENT_USER\SOFTWARE\Microsoft\Fiddler2. Set the DWORD to port 80 (choose decimal here). Restart Fiddler.

enter image description here

  1. Add port 8888 to the addresses defined in your client. For example localhost:8888/MyService/WebAPI/v1/

Solution 7 - Localhost

Using Fiddler v4.6 and the default configuration could not see any traffic from 'localhost'. Tried many suggestions here but nothing worked.

Enabled Help -> Troubleshot and could see many more requests. Sessions were marked in a strike-through font and reason given was 'Hidden due to Status Bar> Process Filter.'

Found this reply from Eric Lawrence to person having same problem http://www.telerik.com/forums/fiddler-not-capturing-ios-traffic-even-though-echo-service-works

basically what to do is: Look at the Status Bar across the bottom of the Fiddler window, the second little "tray" in that bar probably says something like "Web Browsers." Click that and then change to "All Processes."

Fiddler Status Bar

Solution 8 - Localhost

You can use http://ipv4.fiddler or http://ipv6.fiddler instead of localhost

Solution 9 - Localhost

Don't use localhost in the url!

  • http://localhost:4200/myTestProject

Use like this:


=>=> Click here for further information <=<=

Solution 10 - Localhost

make sure Monitor all connections is ticked. it does not work for me maybe port is diffren i need yo see httprequest to my site from gmail my site is on win xp and iis5(my own machine)

Solution 11 - Localhost

Use your local IP address (not 127.0.0.1) instead would work, such as 192.16.0.88 etc. Go to cmd.exe and type ipconfig and you will see it.

alt text

Solution 12 - Localhost

Windows XP:

Be sure to set to click the settings button for each of the items in the "Dial-up and Virtual Private Network settings" listbox in the "Connections" tab of the "Internet Options" control panel applet.

I noticed that Fiddler would stop using the "LAN settings" configuration once I connected to my VPN. Even if the traffic wasn't going through the VPN.

Solution 13 - Localhost

  • Type ipconfig at the commmand prompt.
  • It will give you your IPv4 Address
  • Replace localhost with your IPv4 Address in the Url when hitting the service.

The traffic will show up in Fiddler under your computer's IP address.

Solution 14 - Localhost

Unfortunately none of the suggestions were helpful

Only complete exclusion of localhost from monitoring with following setting:

Open View Menu
  > Preferences
    > Connections
      > Bypass Fiddler for URLs that start with:
        > localhost;127.0.0.1

Solution 15 - Localhost

Go to Tools, Fiddler Options ..., select the Connections tab, then make sure Monitor all connections is ticked. Like Antony Scott said, but also make sure that the "Web Sessions" pane is set to "Capturing" and [ "Web Browsers" OR "All Processes" ]. Looks like the default is "Non-Browser".

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
QuestionNotMyselfView Question on Stackoverflow
Solution 1 - LocalhostNotMyselfView Answer on Stackoverflow
Solution 2 - LocalhostMatt DillardView Answer on Stackoverflow
Solution 3 - LocalhostEric LawrenceView Answer on Stackoverflow
Solution 4 - LocalhostJonathanView Answer on Stackoverflow
Solution 5 - LocalhostPiskvor left the buildingView Answer on Stackoverflow
Solution 6 - LocalhostozanmutView Answer on Stackoverflow
Solution 7 - LocalhostRicardo stands with UkraineView Answer on Stackoverflow
Solution 8 - LocalhostmodeebView Answer on Stackoverflow
Solution 9 - LocalhostAlper EbicogluView Answer on Stackoverflow
Solution 10 - Localhostuser88064View Answer on Stackoverflow
Solution 11 - Localhostschrodinger's codeView Answer on Stackoverflow
Solution 12 - LocalhostUser1View Answer on Stackoverflow
Solution 13 - LocalhostChristian FindlayView Answer on Stackoverflow
Solution 14 - LocalhostSteven PribilinskiyView Answer on Stackoverflow
Solution 15 - LocalhostMarcusView Answer on Stackoverflow