Capturing Localhost Traffic
|Product Version||1.0.0 and above|
While testing my application the traffic sent to http://localhost or http://127.0.0.1 is not captured by Fiddler Everywhere system capturing. How can I handle this issue?
Some frameworks (like .NET) are not proxying the localhost traffic. To solve that issue, you can utilize either of the following approaches:
Use the machine name instead of
- Use one of the specially provided aliases in Fiddler Everywhere.
Both solutions require you to enable the Capturing mode.
Using the Machine Name
Use the machine name as an alias for
localhost or the
127.0.0.1 loopback addresses. For example, if the machine name is
http://myrootuserid:8081/mytestpage.aspx in the Shell.
Depending on the specific scenario, you can replace
127.0.0.1 with one of the following special Fiddler aliases:
ipv4.fiddlerfor connections using Internet Protocol version 4.
ipv6.fiddlerfor connections using Internet Protocol version 6.
Hostheader (applicable for IIS Express).
For example, traffic sent to the following URL may not be captured:
To capture that traffic with Fiddler Everywhere, use any of the following approaches:
ipv4.fiddleralias to hit
localhostwith the ipv6.fiddler alias to hit
localhost.fiddleralias to hit
Filtering Localhost Traffic
While using one of the above solutions to capture localhost requests, the traffic will be captured in the Live Traffic list, and the loopback address will be displayed as a host name, usually
127.0.0.1. To filter by the Host column so that only localhost traffic is displayed, enter the loopback address, and not the aliases used in the browsers, as a
If you have more questions or need assistance capturing localhost traffic with Fiddler Everywhere, you can reach out to our support team through the Help > **Contact Support* option.