GET vs POST

[TimTimTimma]

Ok, today I realized that when using the GET method there is a MAXIMUM amount of information that can be processed, I tried to create something using a form equipped with the get method and I got a "the url is WAY TO LONG" error message. I then switched it over to post and the data went through everything worked. My Question is, should I use POST in all the forms I use or certain ones. And if only certain ones which ones? And to end it all what is different between GET and POST besides the fact that one displays info in browser and other doesnt.

[jansky]

read this

[planetsim]

GET String is in the URL bar e.g.

url.php?test=var

GET can only retrieve the $_GET['test'] and var would be the output. Yes the QueryString has limitation on how many characters you can have within it this is to try and protect against malicious use.

POST on the other hand is used with FORMS and has a set memory allowed in the php.ini oh how much data can be processed in one POST method. In a phpinfo page you can view that by looking for post_max_size default setting to 8M.

If your going to be using forms your best to use the POST method especially bigger forms as there is a better chance that you wont get any errors such as URL to long. (Which It has slipped my mind on how many characters you can have).

[cretaceous]

also the idea is that get is for a query that does not alter the database while post enters data or modifies a db

thats why if you hit 'back' and return to a 'post' form page, the browser gives you a warning (that is unless you switch that warning off)

this page explains:
http://www.cs.tut.fi/~jkorpela/forms/methods.html

[onedrum]

I'm sure the 2 linked docos mention this, but just in case they don't or like me you haven't read them yet,

One handy thing about using GET is that it can be bookmarked by the user. POST cannot.