The usual network parameters, whether get or POST, are basically passing an object/dictionary to the server. Except for changing the request type, there is basically no difference between passing parameters. In fact, the system or three parties give us the processing of parameters, and the actual processing method is different.

Arguments passed in get requests are eventually explicitly concatenated to the URL, such as:… loginin? username=123&password=123

The parameters passed by POST are actually passed in the data segment of the network request and are not explicitly exposed on the link

Query is actually a get request (post can also be passed this way) that concatenates the parameters to the URL, such as:… loginin? username=123&password=123

The body parameter type can only be passed by post, which means that the passed parameter ends up in the data field, rather than after the URL like get. For example: URL :… Loginin data segment :username and password

Here’s an example:

Basic links:… loginin

URL parameter stitching: URL +? Parameter = Parameter content & Parameter = Parameter type &…

1. Request mode: GET

Parameters: name + request type + data type

username	query 	string
password	query 	string
Copy the code

The actual GET request passes the parameters username and password

The final submission url is… loginin? Username =123&password=123 None Data section

2. Request mode: POST

Parameters: name + request type + data type

username	query	string
password 	query	string

key 		body 	string
id			body	string
			
Copy the code

You can see that the username and password are passed from get to query.

The key and ID are of type body, and the passed parameters are put on the data side, that is, just like the normal POST passed parameters, and finally passed to the data segment

The final submission url is… loginin? Username =123&password=123 data Specifies the key and ID