A:
the Get: get an entity by way of resource information specified by the request URI, if the request URI is simply a data generating process, the final entity to be returned in the response is the result of processing resources directed, rather than the processing description of the process.
Post: sent to the server object to the request to accept the entity enclosed in the request, and treat it as a new subordinate of the request queue in the request URI specified resource, Post method is designed to achieve the following unified features:
1: interpretation of existing resources
2: the electronic bulletin boards, newsgroups, mailing lists or discussion groups sent similar information.
3: Submit Data Block
4: Extending a database through an append operation
described can be seen from the above, the server for the Get request is sent to obtain data; Post submitted the request for one kind of data to the server, to submit the data information located entity behind the head.
The difference between get and post form submission embodiment has 5:00
1.get data is acquired from the server, the server transmits data to a post.
2.get is added to the parameter data queue ACTION attribute of a form submission URL referred to in the various fields and values within the form-one correspondence can be seen in the URL. post by HTTPpost mechanism to various fields with its contents is placed in a form HTML HEADER URL address transmitted with the ACTION attribute refers. Users do not see this process.
3. For get embodiment, a server Request.QueryString variable value acquisition for post embodiment, the server acquires data submitted by Request.Form.
4.get transfer data amount is small, not greater than 2KB. post large amount of data transmission, typically default to unlimited. But in theory, IIS4 the maximum amount of 80KB, IIS5 for 100KB.
5.get security is very low, post high security.
HTTP request: the difference between get and post methods of
HTTP defines different ways to interact with the server, the most basic method is to get and post. In fact get for most requests, while retaining the post only for the update site. According to the HTTP specification, get the information for retrieval and should be safe and idempotent. The so-called security means that the operation used to obtain information rather than modify the information. In other words, get requests should generally be free of side effects. Power and other means of multiple requests for the same URL should return the same result. Complete definition is not as strict as it seems. Fundamentally, the goal is that when a user opens a link, she can be sure that from their own point of view does not change the resource. For example, the front page of a news site constantly updated. Although the second request will return a different batch of news, this operation is still considered safe and idempotent, because it always returns the current news. vice versa. post request is not so easy. post requests that may modify resources on the server. Still news site, for example, readers should comment on the article by post that request, because after the notes have been submitted to the site is different (for example appears below the article notes);
when FORM submit, if not specified Method, the default request to get the data submitted in the Form will be appended to the url, to? separate separately from the url. It is transmitted as alphanumeric characters, but the space is converted to a "+", and other symbols are converted to% XX, where XX is the symbol for the hexadecimal ASCII (or ISOLatin-1) represented by the value. Please get request submitted protocol data is placed in the HTTP request header, and the data is placed in post submitted data entity;