The use of Inspectors in the advanced toolbar of Fiddler packet capture tool

Use of Inspectors in the Advanced Toolbar

The Inspectors tab allows you to view the content of each request and response in a number of different formats. JPG format can use ImageView to see the picture, HTML/JS/CSS can use TextView to see the content of the response. The Raw tab allows you to view raw HTTP-compliant request and response headers. The Cookies tab can see the requested cookie and the set-cookie header information of the response

The Inspectors tab is divided into upper and lower parts. The upper part displays the information related to the sent request, and the lower part displays the information related to the received response.

Request section

Headers : Displays the header of the HTTP request sent by the client to the server, displayed as a hierarchical view, including web client information, cookies, security, transmission status, etc.

Textview:  Display the body part of the POST request as text

WebForms: Display the GET parameters of the request and the content of the POST body. In particular, the QueryString here is the content following the url; the body here is in the application/x-www-form-urlen-coded format

HexView:  display requests with hexadecimal data

Auth: Display the Proxy-Authorization and Authorization information in the header

Cookies: display requested cookie information 

Raw : Display the entire request as plain text, the most original format (used more)

JSON: display information in json format

XML: If the requested body is in XML format, a hierarchical XML tree is used to display it

 Response section

Transformer: Displays the encoding information of the response

Sometimes the returned data is too large, and the data will be encoded or compressed (such as GZIP), and it needs to be converted before it can be browsed normally in TextView. Click this area or the Remove HTTP Chunked Encoding button below to perform conversion or decompression. This prompt is invisible if the request is not encoded/compressed.

HTTP Compression displays the encoding method used by the current request. There is no compression here, so it is displayed as None
 

Headers : display the headers of the response

TextView:  Use text to display the corresponding body

ImageVies : If the request is an image resource, display the image in response

The left area will display information such as the size, width, height, and file format of the image

You can also choose the zoom mode below: auto zoom, zoom to fit the size of the display area, no zoom

HexView :  Display responses with hexadecimal data

WebView : Respond to the preview effect in the web browser

Auth: Display the Proxy-Authorization and Authorization information in the response header

Caching:  Display cache information for this request

 Cookies: display the returned cookie information

Raw :  Display the entire response as plain text

JSON: If the returned response content is in json format, it will be displayed here

XML: If the corresponding body is in XML format, a hierarchical XML tree is used to display it

Practical case

Optical theory is useless, you have to learn to follow along, and you have to do it yourself, so that you can apply what you have learned to practice. At this time, you can learn from some actual combat cases.

If it is helpful to you, please like and collect it to give the author an encouragement. It is also convenient for you to quickly find it next time.

If you don’t understand, please consult the small card below. The blogger also hopes to learn and progress with like-minded testers

At the right age, choose the right position, and try to give full play to your own advantages.

My road of automated test development is inseparable from the plan of each stage along the way, because I like planning and summarizing,

Test and develop video tutorials, study notes and receive portals! ! !

Guess you like

Origin blog.csdn.net/Liuyanan990830/article/details/131046674