with - http post example
What is the difference between POST and GET? (6)
Learn underlaying HTTP Protocol
This is similar to driving a car. You buy yourself a car and go on the road, but you don't know any of the signs, lights or other rules you must obey. Obviously you're not able to drive even though you know how to manage a car. At least not safely. Not for yourself, neither for others.
You should learn a bit about HTTP protocol. GET/POST are not related (at least not directly) to PHP/AJAX/jQuery or similar. They use them because they are using HTTP protocol for communication. And there's much more to HTTP Protocol than just
Check out some of these and then search on your own as well:
This question already has an answer here:
I've only recently been getting involved with PHP/AJAX/jQuery and it seems to me that an important part of these technologies is that of
First, what is the difference between
GET? Through experimenting, I know that
GET appends the returning variables and their values to the URL string
So, is this the only difference or are there specific rules or conventions for using one or the other?
Second, I've also seen
GET outside of PHP: also in AJAX and jQuery. How do
GET differ between these 3? Are they the same idea, same functionality, just utilized differently?
POST are two different types of HTTP requests.
According to Wikipedia:
GET requests a representation of the specified resource. Note that GET should not be used for operations that cause side-effects, such as using it for taking actions in web applications. One reason for this is that GET may be used arbitrarily by robots or crawlers, which should not need to consider the side effects that a request should cause.
POST submits data to be processed (e.g., from an HTML form) to the identified resource. The data is included in the body of the request. This may result in the creation of a new resource or the updates of existing resources or both.
GET is used to retrieve remote data, and
POST is used to insert/update remote data.
HTTP/1.1 specification (RFC 2616) section 9 Method Definitions contains more information on
POSTas well as the other HTTP methods, if you are interested.
In addition to explaining the intended uses of each method, the spec also provides at least one practical reason for why
GET should only be used to retrieve data:
Authors of services which use the HTTP protocol SHOULD NOT use GET based forms for the submission of sensitive data, because this will cause this data to be encoded in the Request-URI. Many existing servers, proxies, and user agents will log the request URI in some place where it might be visible to third parties. Servers can use POST-based form submission instead
Finally, an important consideration when using
GETfor AJAX requests is that some browsers - IE in particular - will cache the results of a
GETrequest. So if you, for example, poll using the same
GETrequest you will always get back the same results, even if the data you are querying is being updated server-side. One way to alleviate this problem is to make the URL unique for each request by appending a timestamp.
If you are working RESTfully, GET should be used for requests where you are only getting data, and POST should be used for requests where you are making something happen.
GET the page showing a particular SO question
POST a comment
Send a POST request by clicking the "Add to cart" button.
POST and GET are two HTTP request methods. GET is usually intended to retrieve some data, and is expected to be idempotent (repeating the query does not have any side-effects) and can only send limited amounts of parameter data to the server. GET requests are often cached by default by some browsers if you are not careful.
POST is intended for changing the server state. It carries more data, and repeating the query is allowed (and often expected) to have side-effects such as creating two messages instead of one.
Whilst not a description of the differences, below are a couple of things to think about when choosing the correct method.
- GET requests can get cached by the browser which can be a problem (or benefit) when using ajax.
- GET requests expose parameters to users (POST does as well but they are less visible).
- POST can pass much more information to the server and can be of almost any length.
With POST you can also do multipart mime encoding which means you can attach files as well. Also if you are using post variables across navigation of pages, the user will get a warning asking if they want to resubmit the post parameter. Typically they look the same in an HTTP request, but you should just stick to POST if you need to "POST" something TO a server and "GET" if you need to GET something FROM a server as that's the way they were intended.