Get vs Post - Difference and Comparison

Also Compare

Cameras Cars Cell Phones GPS Systems Processors Tennis Players more..

From Diffen

To choose between Get and Post, rate them on the comparison parameters by entering scores (+ve or -ve) in the comparison tool. The total points are automatically shown in the top row. This should help you decide.

Get

Post

Currently 3.33/5
1
2
3
4
5

Rating: 3.3/5 (48 votes)

Currently 3.91/5
1
2
3
4
5

Rating: 3.9/5 (56 votes)

Encoding type (enctype attribute):

application/x-www-form-urlencoded

multipart/form-data or application/x-www-form-urlencoded

Security:

GET is less secure compared to POST

POST is safer than GET

Restrictions on form data length:

Yes, since form data is in the URL and URL length is restricted

No restrictions

Restrictions on form data type:

Yes, only ASCII characters allowed.

No restrictions. Binary data is also allowed.

BACK button/re-submit behaviour:

GET requests are re-executed.

The browser usually alerts the user that data will need to be re-submitted.

In HTML, one can specify two different submission methods for a form. The method is specified inside a FORM element, using the METHOD attribute. The difference between METHOD="GET" (the default) and METHOD="POST" is primarily defined in terms of form data encoding. According to the technical HTML specifications GET means that form data is to be encoded (by a browser) into a URL while POST means that the form data is to appear within the message body of the HTTP request.

1 Differences in form submission
- 1.1 Pros and Cons
2 Differences in server-side processing
3 Recommended Usage
4 See Also
5 References

[edit] Differences in form submission

The fundamental difference between METHOD="GET" and METHOD="POST" is that they correspond to different HTTP requests, as defined in the HTTP specifications. The submission process for both methods begins in the same way - a form data set is constructed by the browser and then encoded in a manner specified by the enctype attribute. For METHOD="POST the enctype attribute can be multipart/form-data or application/x-www-form-urlencoded, whereas for METHOD="GET", only application/x-www-form-urlencoded is allowed. This form data set is then transmitted to the server.

For form submission with METHOD="GET", the browser constructs a URL by taking the value of the action attribute, appending a ? to it, then appending the form data set (encoded using the application/x-www-form-urlencoded content type). The browser then processes this URL as if following a link (or as if the user had typed the URL directly). The browser divides the URL into parts and recognizes a host, then sends to that host a GET request with the rest of the URL as argument. The server takes it from there. Note that this process means that the form data are restricted to ASCII codes. Special care should be taken to encode and decode other types of characters when passing them through the URL in ASCII format.

Submission of a form with METHOD="POST" causes a POST request to be sent, using the value of the action attribute and a message created according to the content type specified by the enctype attribute.

[edit] Pros and Cons

Since form data is sent as part of the URL when GET is used --

Form data are restricted to ASCII codes. Special care should be taken to encode and decode other types of characters when passing them through the URL in ASCII format. On the other hand, binary data, images and other files can all be submitted through METHOD="POST"
All form data filled in is visible in the URL. Moreover, it is also stored in the user's web browsing history/logs for the browser. These issues make GET less secure.
However, one advantage of form data being sent as part of the URL is that one can bookmark the URLs and directly use them and completely bypass the form-filling process.
There is a limitation on how much form data can be sent because URL lengths are limited.

[edit] Differences in server-side processing

In principle, processing of a submitted form data depends on whether it is sent with METHOD="GET" or METHOD="POST". Since the data is encoded in different ways, different decoding mechanisms are needed. Thus, generally speaking, changing the METHOD may necessitate a change in the script which processes the submission. For example, when using the CGI interface, the script receives the data in an environment variable (QUERYSTRING) when GET is used. But when POST is used, form data is passed in the standard input stream (stdin) and the number of bytes to be read is given by the Content-length header.

[edit] Recommended Usage

GET is recommended when submitting "idempotent" forms - those that do not 'significantly alter the state of the world'. In other words, forms that involve database queries only. Another perspective is that several idempotent queries will have the same effect as a single query. If database updates or other actions such as triggering emails are involved, the usage of POST is recommended.

A "GET" request is often cacheable, whereas a "POST" request can hardly be. For query systems this may have a considerable efficiency impact, especially if the query strings are simple, since caches might serve the most frequent queries.

In certain cases, using POST is recommended even for idempotent queries:

If the form data would contain non-ASCII characters (such as accented characters), then METHOD="GET" is inapplicable in principle, although it may work in practice (mainly for ISO Latin 1 characters).
If the form data set is large - say, hundreds of characters - then METHOD="GET" may cause practical problems with implementations which cannot handle that long URLs.
You might wish to avoid METHOD="GET" in order to make it less visible to users how the form works, especially in order to make "hidden" fields (INPUT TYPE="HIDDEN") more hidden by not appearing in the URL. But even if you use hidden fields with METHOD="POST", they will still appear in the HTML source code.