Preparing for Java and Spring Boot Interview?

Join my Newsletter, its FREE

Sunday, July 25, 2021

What is GET and POST method in HTTP and HTTPS Protocol? Answer

GET and POST method in HTTP and HTTPS are two most popular methods used to transfer data from client to server using  HTTP(HyperText Transfer Protocol)  protocol. Both GET and POST can be used to send requests and receive response but there are significant differences between them. The difference between GET and POST in HTTP or HTTPS is also a popular interview question in JSP and any web programming interview. Since HTML is independent of any web server technology like Java, ASP or PHP and HTTP is core protocol in space of the internet, the importance of a clear understanding of GET and POST method can not be ignored.

In this tutorial we will What is GET HTTP Request, What is POST HTTP Request When to use GET and POST HTTP method,s and finally some differences between GET and POST method in HTTP protocol.

What is GET HTTP Request in http

difference between GET POST method in HTTP and HTTPS ProtocolHTTP protocol supports several request methods you can use while sending requests using HTTP or HTTPS protocol. GET is one of them. As the name suggests the GET method is to retrieve a page from the HTTP Server. You can identify a GET request by looking method attribute on the HTTP Request part. 

If you are using Netbeans IDE for Java web development you can enable HTTP Server monitor which can capture HTTP requests and show details of request parameters, headers, and other useful information. for GET HTTP request method will be GET for example almost all the URL which is accessible using link are accessed using HTTP Request. 

One important property of GET request is that any request parameter or query parameter is passed as URL encoded string, appended using "?" character which makes it non-secure because whatever information you pass in URL String is visible to everybody. Though GET method has some very interesting and powerful use cases which we will see in the next section: When to use GET HTTP Request?

When to use HTTP GET request

As I said GET method is not secure and hence not a suitable choice for transferring confidential data but GET method is extremely useful for retrieving static content from web server. here are some examples where a using GET method make sense:

1) There is no side effect of repeated request. for example clicking a link which points to another page. it doesn't matter if you click the link twice or thrice , This also gives chance browser of the server to catch the response for faster retrieval.

2) You are not passing any sensitive and confidential information. instead you just passing some configuration data or session id.

3) You want URL pointed by HTTP GET request to be bookmark-able.

4) Data requires to be sent to Server is not large and can safely accommodate in the maximum length of URL supported by all browsers. In general different browser has a different character limit for URL length but having it under the limit is a good choice.

What is the POST HTTP method?

POST HTTP request is denoted by the method: POST in the HTTP request. In POST method data is not sent as part of a URL string to server instead in POST, data is sent as part of message body. Almost all authentication request is sent via POST method in HTTP world. POST method is secure because data is not visible in URL String and can be safely encrypted using HTTPS for further security. 

All sensitive and confidential information sent to be server must go on POST request and via HTTPS (HTTP with SSL). POST method is also used for submitting information to server, any information which can alter state of application like adding item into shopping cart, making payments etc. here are some examples where you should consider using POST method in HTTP request:

1) Use POST if you are sending large data which can not be fit into URL in case of GET.

2) Use the POST method if you are passing sensitive and confidential information to server e.g. user_id, password, account number etc.

3) Use the POST method if you are submitting data that can alter the state of application e.g. adding items into cart for passing that cart for payment processing.

4) Use POST if you are writing a secure application and don't want to show query parameters in the URL. You can further see these Servlet and JSP courses to learn more about the POST method and how they are processed in Java. 

What is GET and POST method in HTTP and HTTPS Protocol? Answer

Difference between GET and POST method in HTTP Protocol

Most of the difference between GET and POST has been already discussed in there respective sections. It all depends upon requirement when you want to choose GET and POST and knowledge of these differences help you to make that decision.

1) GET method passes request parameter in URL String while POST method passes the request parameter in request body.
2) GET request can only pass limited amount of data while POST method can pass large amount of data to server.
3) GET requests can be bookmarked and cached unlike POST requests.
4) GET is mostly used for view purpose (e.g. SQL SELECT) while POST is mainly use for update purpose (e.g. SQL INSERT or UPDATE).

That’s all on What is GET and POST methods in http protocol and difference between GET and POST http request. The key point is to know where to use GET request and where to use POST request.

Other Servlet JSP tutorial you may like:


Anonymous said...

very informative post.. to learn other languages the tutorials available at

Cheng Yim said...

I think one difference between GET and POST in html is enough to describe there basic purpose. GET request is used to retrieve data from Server without changing state of Server while POST request in html is used to send data to server which cause change in Server's state like storing data into Database, Storing XML files etc. Though you have outlined number of differences between GET and POST, which is OK but I think this difference is what differentiate GET with the POST.

Anonymous said...

Cheng, I could not understand one thing in your point. Even in case of GET, data is being transferred to server though in the form of querystring, so data can still change the state of server (like DB storage). Which is applicable in case of POST as well. So tell me where is the diffenence in terms of point you mentioned??

JackTheR said...

Surprised to see, no one has mentioned most obvious difference between GET and POST methods, In my opinion GET is to get data from the Server and POST to post (read send) data to the Server. If you don't agree, let me know WHY?

Unknown said...

JackTheR i see your point........but i would agree with the author though in security issues and when to use between those to....only thing i disagree is sounds that the author pointed that they are all the same except only when it comes to security and other issues mentioned...he never mentioned about POST which is to read data from server to the client?while GET is to write to the server?

YourFriend said...

Nice tutorial
POST method is more secure than GET
Data can be seen in URL when you use GET method
Here is an article about Difference between HTTP and HTTPs

Anonymous said...

I have strong objections to anything in a simple HTTP request ever being called "secure."

The only difference between the visibility of GET and POST data is that it doesn't appear in the URL. It's still completely visible to absolutely everybody who sees the request, including the user (especially with modern browsers like Chrome that have header inspection tools built in), including any malware installed on the user's machine, including anyone on their hub or on an ARP cache poisoned switch, including any points along the route, etc., etc.

Security through obscurity is the exact opposite of security. It creates a false sense of security, leading to complacency, making it even easier for malicious or curious agents to compromise your security.

If you're thinking about security on the web, your very first thought should be TLS (SSL), not GET v. POST.

Post a Comment