http get and post efficiency_html/css_WEB-ITnose

Many people on the Internet say: get is more efficient than post; I don’t understand why?

get: Splice the parameters into a url and put it in the header message header to pass;
post: Store it directly in the message body in the form of key-value pairs and pass it;
Of course, when passing it in post, the message The header will have some additional explanatory information, but it will have minimal impact on efficiency;

Reply to discussion (solution)

post is mainly used for form submission , and get can submit data in the form of URL followed by parameters, so the amount of data transmitted by get is less than that of post, and when the data is cached, get obtains the data directly from the cache, while post obtains data from the server each time it is read.

However, the amount of data transmitted by get is limited, and the security is not as good as post

I can guarantee that if there is not much data, there will be no difference in speed between the two. Don't get too hung up on it. Just as needed.

Generally, we don’t compare get and post efficiency issues, but it depends on the program design which submission is more convenient and more appropriate. For example, if you want to submit a form, even if the post efficiency is lower than get, can you not use it? post?

LZ, for ordinary people, except for the different methods, get and post have little efficiency.
But if you want to dig deeper, there may indeed be some differences.
You can read the following article
http://blog.csdn.net/axman/article/details/7663002

Is there any difference in efficiency? I just know that post is safer.

I’m not going into details, mainly because I think it’s weird that people on the Internet talk about get post efficiency!