3 Answers, 1 is accepted
Hello Somnath Shukla,
Thank you for your interest in Fiddler Everywhere and for your feedback!
Just like the classic Fiddler (and many other applications), the Fiddler Everywhere is hardcoded to bypass proxies for requests targeted to localhost. The only way to circumvent this behavior is to “trick” the applications that they are targeting a remote host. The only way to do this is to use a domain name that differs from the localhost and recognize this domain name in Fiddler to handle the request accordingly. Hence, the various workarounds available: https://docs.telerik.com/fiddler/Configure-Fiddler/Tasks/MonitorLocalTraffic
the above said, instead of typing
http://localhost/some-page
Use the following:
http://ipv4.fiddler/some-page
If your localhost is using a specific port, then pass the port to the Fiddler Everywhere address as well (for example,localhost:4000 becomes ipv4.fiddler:4000).
Regards,
Nick Iliev
Progress Telerik
can u tell me why i have never faced any issue with classic fiddler.
this is the reason i am back to old fiddler.
Hi Somnath,
The alias IPs (like ipv4.fiddler) were introduced in FiddlerCore which is part of both the classic Fiddler and Fiddler Everywhere so it is strange that you are accessing the localhost on the classic Fiddler.
Still, the team acknowledged that this functionality can be improved and is currently looking for a way to provide more seamless usage of localhost. We will post once the full localhost support is introduced in Fiddler Everywhere.
Regards,
Nick Iliev
Progress Telerik