Both GET and POSTt are HTTP requests, so both GET and POST are based on TCP connections.

Nature:

For GET requests, the browser sends both headers and data, and the server responds with data (200ms).

For a POST request, the browser sends the header, the server responds with 100, and the server responds with data for another 200ms

On the surface, GET sends packets only once and POST sends packets twice, so GET is more efficient. However, in a good network environment, the time difference between sending packets can be ignored. In addition, TCP of POST has great advantages in verifying the integrity of packets

Answer:

GET is harmless when the browser falls back, while POST resubmits the request.

The URL generated by GET can be bookmarked, but not by POST.

GET requests are actively cached by browsers, whereas POST requests are not, unless set manually.

GET requests can only be url encoded, while POST supports multiple encoding methods.

GET request parameters are retained in browser history, while parameters in POST are not.

GET requests pass parameters in the URL with length limits, whereas POST does not.

GET accepts only ASCII characters for the data type of the argument, while POST has no restrictions.

GET is less secure than POST because parameters are exposed directly to the URL and therefore cannot be used to pass sensitive information.

The GET argument is passed through the URL, and the POST is placed in the Request body.

Supplement: You can see from NetWork that before sending a formal POST request, an OPTIONS request will be sent first. This is actually a way of processing complex cross-domain requests. Before sending the request, the browser will conduct an OPTIONS pre-request to determine whether the server response is correct and can accept the real request. If the response received after the OPTIONS request is rejected, the server will send the real request Quality, such as 500 HTTP status, then it will stop the second real request access. Ultimately, it’s the difference between how browsers handle simple and complex cross-domain requests