I am sharing my troubleshooting experience using Fiddler Proxy in this post. I often find that using Fiddler is handy as it provides real time visual tracing. It is very useful for App and network troubleshooting.
Reference: https://kb.vmware.com/s/article/50100796
First thing to do is to get the latest version Fiddler installed to your PC. In this tutorial, Fiddler is installed to a Windows 10 PC. You can get Fiddler installation file downloaded from here: https://www.telerik.com/download/fiddler
This is how Fiddler looks like running on a Windows 10 PC
In order to see the data going back and forth between your device and application server, you will need to get HTTPS capture enabled.
Fiddler is by default not allowing other devices to connect. In default mode, you can only use Fiddler as a proxy of your running PC. To allow other devices such as iPhone to connect to it, please turn on “Allow other devices to connect to proxy”. Of course, you will need to make sure your iPhone and Fiddler are connecting to the same WiFi.
To get a iPhone to trust the Fiddler proxy, we have to get the Fiddler certificate installied to a iPhone. You simply open up Safari browser on your iPhone, point it to your Fiddler IP address (e.g. http://192.168.86.207:8888) Make sure you use http, not https in this case to open the Fiddler page. Click FiddlerRoot certificate to get the certificate downloaded to your iPhone.
Getting a certificate downloaded to your iPhone does not make it a trusted certificate to your iPhone automatically. Go to Certificate Trust Settings on your iPhone and make your downloaded Fiddler certificate trusted.
You can now point your iPhone to use the Fiddler as a WiFi network proxy.
Go back to your Fiddler, do some web browsing on your connected iPhone. Now you can intercept all the device traffic !
In case you encounter server identity warning and certificate not trusted warning like , please follow this to get a new fiddler root certificate generated. https://www.telerik.com/blogs/the-certenroll-certificate-generator
Get the new root certificate downloaded again to your iPhone and problem should be gone after iPhone receive a new root certificate.
Comments