Chrome Fiddler redirect HTTPS requests

Principle:
Fiddler will get the browser HTTP request, but to crawl https JS content, fiddler must decrypt HTTPS traffic, but the browser will check the digital certificate, and found that the session was bugged, in order to deceive the browser, Fiddler re-encrypts HTTPS traffic by using another digital certificate. After fiddler is configured to decrypt HTTPS traffic, a CA certificate named Do_not_trust_fiddlerroot is automatically generated and used to issue a TLS certificate for each domain name. If this certificate is listed as a browser or other software in the trusted CA list, then the browser or other software will assume that https painting is trustworthy and will not eject the certificate error warning.

1. Open Fiddler, and in the menu bar, select "Tools", "Fiddler Options", "HTTPS", tick the option.

2. After importing to the desktop, double-click Open, figure below

or open your browser settings, advanced settings privacy settings and security

Chrome Fiddler redirect HTTPS requests