I had a need to debug an external app using fiddler.
Seems to be a trivial exercise, but I could not see the captured traffic in fiddler ?
After Googling a bit, I could only find part of the solution.
Below is the full story.
Solution :
1. Proxy Settings : First of all you need to know that Fiddler acts as a proxy server on your machine when you start it.
The default address / port is 127.0.0.1:8888
You can check the settings after starting Fiddler in you Browser settings.
So you need to set the proxy settings in your local application that you want to test.
2. Decrypt HTTPS settings
Make sure you have set to Decrypt HTTPS
This needs a extra extension to Fiddler (which is not installed by default)
3. Capture all Processes
After that you need to make sure that you tell Fiddler to capture all traffic for all Processes.
This last step I overlooked for a few hours before my eyes caught the option menu at the bottom.
Enjoy
[…] Fiddler – How to capture non Web Browser traffic […]
[…] https://audministrator.wordpress.com/2016/03/21/fiddler-how-to-capture-non-web-browser-traffic/ […]
Good point – it took me a while until I found out how to intercept web traffic not generated by browsers, even more so, by the applications that natively do not support proxies – say, powershell cmdlets. No, “-Proxy” flag in those cmdlets did not work. Fiddler did. Thanks.
Hello, I’m trying to intercept web traffic from a PowerShell script, but cannot seem to generate the traffic in Fiddler. How were you able to capture the request?
Hi,
There different support blogs about this avaible.
Best look here :
https://stackoverflow.com/questions/24936541/fiddler-not-intercepting-powershell-web-requests
https://brianbunke.com/blog/2018/05/02/proxy-to-fiddler/
https://www.cryingcloud.com/blog/2018/10/16/capturing-and-using-api-queries-from-azure-in-powershell-with-fiddler
Hope this can help …