Win a copy of Murach's Python Programming this week in the Jython/Python forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

disadvantages of using POST method in HTTP  RSS feed

 
Anitha Aravind
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello Everyone

I would like to know any disadvantages(if available) of using the post method in the HTTP request.

I have not come across any in the books that I read.

Cheers
Anitha
 
Anitha Aravind
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This question appends the previous post.

Is a new connection created for sending the data thru' the POST method?

Anitha
 
Dicky Bullin
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Anita,

First, I don't know if there's any disadvantages using the POST mehtod. All I know is, if you're sending request using the GET method, all the parameter is shown in the url. But if you're using the POST method, the parameter is not shown in the url. Haha, maybe you're already know it huh? Sorry, but that's what I know for this time.

And for the second, the connection always created for every request, whether a POST request or a GET method. And since HTTP is a stateless protocoll, all of the connection is "a new connection"

Hope this can help you

Regards,

Dicky Bullin

[ September 01, 2004: Message edited by: Dicky Bullin ]
[ September 01, 2004: Message edited by: Dicky Bullin ]
 
Ramaswamy Srinivasan
Ranch Hand
Posts: 295
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Anitha

Well....regarding the POST request, the info provided is not appended to the URL. The GET request takes the parameters directly to the server via the URL but using POST, the info is a part of the request body. That's why we don't come to see the parameters.

I also came to know that POST is not used where any searching is required, since we need to append the info to the URL. I shall update if i get any more information.

Check out whether the info is correct. and revert to me.....plz
 
Bear Bibeault
Author and ninkuma
Marshal
Posts: 65826
134
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I also came to know that POST is not used where any searching is required, since we need to append the info to the URL


??? That makes no sense. Regardless of the purpose of the submission, whether the parameters are passed on the URL or as part of the request body is moot.
 
Ramaswamy Srinivasan
Ranch Hand
Posts: 295
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Bear,

Thanks for pointing out the correction..... By the way, normally in searches, the query parameter is appended to the URL right?

If not kindly clarify
 
Bear Bibeault
Author and ninkuma
Marshal
Posts: 65826
134
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm saying it doesn't matter.
 
Adeel Ansari
Ranch Hand
Posts: 2874
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
- according to the http specifications the GET method is safe and also idempotent

- and POST method may be idempotent

IDEMPOTENT:

An idempotent operation is an operation that if run multiple times has no affect on state. that is, it is query only not update

But again it is not the disadvantage of the post method. there is nothing to stop application to use POST instead of GET.
 
Jose Zaleta
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As I user the only "disadvantage" you might get from using a POST request is that the user may not cache the result.

To summarize:

As Adeel was saying, that's why GET is used in operations that don't really affect the state of an application (like queries), and POST is.

When using GET some browsers and/or servers may limit the quantity of data you can send in the query string. With POST, an advantage is that this limit does not exist.

Both GET and POST are HTTP requests. When the user clicks the link or submit button, a NEW connection will be used to make the request for both cases. So both will have a similar performance. A way to "optimize" this is to use HTTP 1.1 that can make a more efficient use of connections by keeping the same one alive to perform the requested HTTP operation.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!