Fiddler capture configuration

Fiddler capture configuration

Recently, the joint debugging interface, the other party used our interface called by the H5 page embedded in the APP. There were various problems during the use process. I simply checked the usage of Fiddler and directly grabbed the HTTP and HTTPS packages from the outside to see the situation.

Reference link:

Reference link: Certificate installation method for https capture with fiddler on IOS .
Reference link: Packet capture tool Filder captures packets on Android phones .
Reference link: Use Fiddler to capture packets under MacOS .
Reference link: Configure Fiddler under Windows10 system .
Reference Link: chrome browser reports error ERR_SSL_OBSOLETE_VERSION .

1. Environment

Fiddler is installed on Win7 version 4 (version 5 does not support Win7 system)
browser Firefox, Chrome

Two, Fiddler installation and configuration

1. Execute the installer directly
   

2. Configure Fiddler
   to configure the HTTPS option
   to trust the Root certificate, and export the Fiddler certificate (save and prepare to import to the monitored end).
   Configure connection options
   

3. After restarting Fiddler,
   close and restart, the settings will take effect

4. Get the IP address of the Fiddler host
   

2. Installation and configuration of the controlled terminal

1. Make sure that the controlled end is in the same network as Fiddler.
   Test that the controlled end can access Fiddler's proxy port (the above setting port is 8888)

2. Install the certificate
   Copy the exported certificate file to the system, double-click to activate "Keychain Access"
   

3. Import the certificate to the specified location
   

4. Modify the certificate trust to "always trust"
   

3. Browser proxy configuration

1. The Firefox browser
   proxy IP and port are the previous configuration of Fiddler
   
2. Chrome browser
   After chrome is upgraded to version 84, the Tls1.3 encryption protocol is enabled by default, and the Tls1.2|1.1|1.0 protocol is discarded. Due to the inconsistency between the browser server (Tls1.2) and client (Tls1.3) encryption protocols, the handshake fails
   Manual solutions
   Solution one: chrome://flags - disabling the Enforce deprecation of legacy TLS versions item temporarily solves the problem.
   
   Configure the Chrome proxy
   
   to be consistent with the Fiddler configuration.
   

4. Test the packet capture function

Open the browser and visit the page to view the data capture on the Fiddler side