Shulou(Shulou.com)06/02 Report--

Http protocol debugging agent tool Fiddler how to use, many novices are not very clear about this, in order to help you solve this problem, the following editor will explain in detail for you, people with this need can come to learn, I hope you can gain something.

Fiddler is a WEB debugging tool that records all client-to-server HTTP requests. When Fiddler starts, it will default to proxy IE browser 127.0.0.1 IE 8888, and other browsers should be set manually.

How it works:

Fiddler works as a proxy WEB server, using proxy address: 127.0.0.1 port: 8888

Fiddler crawls HTTPS settings:

1. Start Fiddler, open Tools > Telerik Fiddler Options in the menu bar, and open the Fiddler Options dialog box.

two。 Set up the Fiddler:

Open the toolbar-> Tools- > Fiddler Options- > HTTPS

Check Capture HTTPS CONNECTS (capture HTTPS connection)

Check Decrypt HTTPS traffic (decrypt HTTPS traffic)

In addition, set Fiddler to get the https requests of all processes on the machine, so select from all process (from all processes) in the middle drop-down menu

Select the ignore server certificat errors below (ignore server certificate error)

3. Configure the windows trust root certificate for Fiddler to resolve the security warning: Trust Root Certificate (trusted root certificate)

4.Fiddler main menu Tools-> Fiddler Options-> Connections

Check Allow remote computers to connect (allow remote connections)

Act as system proxy on startup (as the system startup agent)

5. Restart Fiddler for configuration to take effect (necessary)

Fiddler captures the session of Chrome:

1. Install the SwitchyOmega Agent Chrome browser plug-in

two。 As shown in the figure, set the proxy server to 127.0.0.1purpur8888

3. Switch the set proxy through the browser plug-in

Fiddler interface:

After setting up, native HTTP traffic will be intercepted by Fiddler through 127.0.0.1 8888 proxy.

The request (Request) section explains in detail:

Headers-displays the header of HTTP requests sent by the client to the server as a hierarchical view containing Web client information, Cookie, transfer status, and so on. Textview-shows that the body portion of the POST request is text. WebForms-displays the GET parameters and POST body contents of the request. HexView-displays the request in hexadecimal data. Auth-- displays the Proxy-Authorization (proxy authentication) and Authorization (authorization) information in the response header. Raw-- displays the entire request as plain text. JSON-displays files in JSON format. XML-if the requested body is in XML format, it is displayed in a hierarchical XML tree.

The response (Response) section explains in detail:

Transformer-displays the encoded information of the response. Headers-displays the header of the response in a hierarchical view. TextView-use text to display the corresponding body. ImageVies-if the request is a picture resource, the picture of the response is displayed. HexView-displays the response with hexadecimal data. WebView-responds to the preview effect in the Web browser. Auth-displays Proxy-Authorization (Agent Authentication) and Authorization (Authorization) information in the response header. Caching-displays the cache information for this request. Privacy-displays private (P3P) information for this request. Raw-displays the entire response as plain text. JSON-displays files in JSON format. XML-if the body of the response is in XML format, it is displayed in a hierarchical XML tree. Is it helpful for you to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.