You should start by reading this thread, which explains what a HTTP CONNECT Tunnel is: https://groups.google.com/forum/#!topic/httpfiddler/RCkzE3HhhxY Since you have enabled decryption, if you’re not seeing any HTTPS traffic in Fiddler, you either have a Filter enabled (click Help > Troubleshoot Filters) or you have not configured Windows to trust the Fiddler root certificate and hence … Read more
I updated Fiddler and ran into a similar issue. This fixed it for me: http://textslashplain.com/2015/10/30/reset-fiddlers-https-certificates/ Fiddler 1.3.0+ (This is the new build and comes after 4.6.1.5+) Click Settings (the cog in the top right hand corner). Select the HTTPS tab from the left hand panel Click Trust root certificate Accept all prompts You may need … Read more
What you need to do is configure Fiddler to work as a “reverse proxy” There are instructions on 2 different ways you can do this on Fiddler’s website. Here is a copy of the steps: Step #0 Before either of the following options will work, you must enable other computers to connect to Fiddler. To … Read more
try using this: http://ipv4.fiddler/folder instead of http://localhost/folder this also works with ports http://ipv4.fiddler:12345/folder Here is link to fiddler documentation http://docs.telerik.com/fiddler/Configure-Fiddler/Tasks/MonitorLocalTraffic
There’s an easier way now (as of v4.4.5.1 or earlier). Right-click the column bar and select Customize columns…. Collection: Miscellaneous Field Name: RequestMethod Result:
Wireshark, Firebug, Fiddler all do similar things – capture network traffic. Wireshark captures any kind of network packet. It can capture packet details below TCP/IP (HTTP is at the top). It does have filters to reduce the noise it captures. Firebug tracks each request the browser page makes and captures the associated headers and the … Read more
Either of two ways: 1) Disable HTTPS decryption and click the button titled “Remove Interception Certificates” 2) Open CertMgr.msc, open the Personal and Trusted Stores, and use the Delete key on the root.
You need to add this in your web.config <system.net> <defaultProxy> <proxy bypassonlocal=”False” usesystemdefault=”True” proxyaddress=”http://127.0.0.1:8888″ /> </defaultProxy> </system.net> then Start Fiddler on the WEBSERVER machine. Click Tools | Fiddler Options => Connections => adjust the port as 8888.(allow remote if you need that) Ok, then from file menu, capture the traffic. That’s all, but don’t forget … Read more
This is easy to do. On the filters tab, click “show only if the filter contains, and then key in your domain.
By simply adding fiddler to the url http://localhost.fiddler:8081/ Traffic is routed through fiddler and therefore being displayed on fiddler.