Download address:
https://www.telerik.com/download/fiddler

First, Composer Introduction

The Composer area on the right is the interface of the test interface:

Fiddler_interface_test_0.png

Related instructions:

1. Request method: Click to open the request agreement is get, post, etc.

2.url address bar: enter the requested url address

3. Request header: The third block area can input the request header information.

4. Request body:post request to enter body information in this area

5. Execution: After the Execute button is clicked, the request can be executed.

6.http version: you can check the http version

7. Request history: history will be generated in the History area on the right after the execution is completed.

 

Second, the simulation get request

1. Enter the Url address in the address field of the Composer area:

2. Select the get request, click Execute to execute, the request can be sent successfully.

3. After the request is successfully sent, a session record is generated in the left session frame, and the packet capture details can be viewed.

4. There will be one more history request record in the history area on the right.

Fiddler_interface_test_1.png

5. Select the record in the session box to view the test results:

– Select the session and click on Inspectors

–response area to open the Raw area

–Raw looks at the data of the HTML source code

— You can also click on the WebView to view the returned web page data.

Fiddler_interface_test_2.png

 

Third, Json data

1. Some post request parameters and return parameters are in Json format, such as the blog garden login request: https://passport.cnblogs.com/user/signin

2. View json data as shown below

Fiddler_interface_test_3.png

 

Fourth, simulate post request

1. Request type check post

2. url address bar enter the corresponding request address

3. body area write login json parameters

4.header request header area, you can copy the data of the previous capture packet

(Note that some requests will fail if the request header is empty)

Fiddler_interface_test_4.png

5. View the test results after successful execution:

— Execution succeeds as shown in the third figure, showing success=True

–Execution failed as shown below, showing

Message=Invalid length for a Base-64 char array or string.

Success=False

Fiddler_interface_test_5.png

Six: repeated concurrent tests:

Right click on the intercepted url, ->replay -> shift+reissue request to set the number of accesses, such as 100, then click OK.

Content from:

Https://www.cnblogs.com/yoyoketang/p/6754560.html

Https://blog.csdn.net/ziyuxuan90/article/details/81185617

Orignal link:https://www.cnblogs.com/cyq1162/p/10574607.html