Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

GET\POST

 
Balaji Loganathan
author and deputy
Bartender
Posts: 3150
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
Technically what the merits and demerits of using GET or POST.
GET has limation on data size,whereelse POST doesn't,
GET is URL encoded and POST is form encoded.

Please someother important issues.
Regards
Balaji
 
Ivan Tamayo
Ranch Hand
Posts: 49
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If your servlet implements the doGet method, you can call directly:
http://yourserver.com:8080/servlet/Sample
But if the servlet has only the doPost method, you cannot call it this way.
 
sandy gupta
Ranch Hand
Posts: 228
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
get makes only one connection to the server while as post does a roundtrip and then back
 
Balaji Loganathan
author and deputy
Bartender
Posts: 3150
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Please can u explain me further,I'm not getting!
Originally posted by sandy ind:
get makes only one connection to the server while as post does a roundtrip and then back
 
Bosun Bello
Ranch Hand
Posts: 1511
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sandy, I am not sure I get what you meant.
Balaji, it's not only a matter of merit/demerit, it also depens on what you want to do. If you have sensive data that you don't want in the URL, you have to use POST. As you posted, GET also has limitations on the size of the data. If you want to handle both, you can just have one call the other.
 
Balaji Loganathan
author and deputy
Bartender
Posts: 3150
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Bosun,
Well! Even if i send my sensitive data via POST what is the probability that it won't be seen,fo course its not transparent.
I believe a network hacker can easily trap the sensitive data whether it is GET/POST.
I want to know why many web languages are created with GET in mind,for example "Adobe e-forms",
Is there is any performance issues in it. ?


Originally posted by Bosun Bello:
Sandy, I am not sure I get what you meant.
Balaji, it's not only a matter of merit/demerit, it also depens on what you want to do. If you have sensive data that you don't want in the URL, you have to use POST. As you posted, GET also has limitations on the size of the data. If you want to handle both, you can just have one call the other.
 
Manish Hatwalne
Ranch Hand
Posts: 2595
Android Firefox Browser Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
With GET user can bookmark your webpage, and return to it whenever he wants, hoping that he would still get the same info on ur site that he got earlier. Knowing this, u can decide if you want to put sth like session ID embeded in ur URL with GET or not. It entirely depends on ur requirement/design. Besides size, POST makes it a bit more difficult to view the data being posted to the site.
HTH,
- Manish
 
Juanjo Bazan
Ranch Hand
Posts: 231
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You can consider GET as a little more insecure because all data sent with GET method is save in the server's log files(and/or in the client cache), that could be sniffed later by some non-authorized person.
-HTH
Juanjo
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic