The HTTPGet protocol creates a query string of the name-and-value pairs and then appends the query string to the URL of the script on the server that handles the request. Therefore, you can mark the request.
The HTTPPost protocol passes the name-and-value pairs in the body of the HTTP request message.
Length -
Since, HTTPGet request goes via URL, so it has a limitation for its length. It can’t be more than 255 characters long (though this is browser dependent, but usually the max is 255 characters only).
Whereas
No such maximum length limitation holds for the HTTPPost request for the obvious reason that it becomes a part of the body of the HTTP request and there is no size limitation for the body of an HTTP request/response.
Performance -
HTTPGet request is comparatively faster as it’s relatively simpler to create a GET request and
the time spent in the encapsulation of the HTTPPost request in the HTTP body is saved in this case. In addition, the maximum length restriction facilitates better optimization of HTTPGet implementation.
Type of Data -
HTTPGet request is sent via URL string and as we all know that URL can be text-only, so GET can carry only text data
whereas
HTTPPost has no such restriction and it can carry both text as well as binary data.
Caching/Bookmarking – again for the obvious reason that a HTTPGet request is nothing but an URL hence it can be cached as well as Bookmarked.
No such luxuries with a HTTPPost request.
FORM Default -
HTTPGet is the default method of the HTML FORM element.
To submit a FORM using POST method, we need to specify the method attribute and give it the value “HTTPPost”.