GET or POST method?

[Kurda Yon]

Hi,

I have to decide which form-method I should use (GET or POST). I found
the following recomendation:
If the service associated with the processing of a form has side
effects (for example, modification of a database or subscription to a
service), the method should be POST. (http://www.cs.tut.fi/~jkorpela/
forms/methods.html).

However, later I did not find any convinced arguments why it should
help (it can be that I just did not understand something).

So, I have decided not to go into the details of GET and POST methods
and just use POST. Is here any significant difference between GET and
POST which I should worry about (like security issues or something
else)? Or it is just question of convenience?

[Manuel Lemos]

Hello,

on 01/15/2008 12:19 AM Kurda Yon said the following:

Hi,

I have to decide which form-method I should use (GET or POST). I found
the following recomendation:
If the service associated with the processing of a form has side
effects (for example, modification of a database or subscription to a
service), the method should be POST. (http://www.cs.tut.fi/~jkorpela/
forms/methods.html).

However, later I did not find any convinced arguments why it should
help (it can be that I just did not understand something).

So, I have decided not to go into the details of GET and POST methods
and just use POST. Is here any significant difference between GET and
POST which I should worry about (like security issues or something
else)? Or it is just question of convenience?

I think with GET you are limited to sending with no more than 255
characters. Above that the browser may chop your submission URL.

--

Regards,
Manuel Lemos

PHP professionals looking for PHP jobs
http://www.phpclasses.org/professionals/

PHP Classes - Free ready to use OOP components written in PHP
http://www.phpclasses.org/

[David Gillen]

On Tue, 15 Jan 2008 Kurda Yon <ku******@yahoo.comwrote:

Hi,

I have to decide which form-method I should use (GET or POST). I found
the following recomendation:
If the service associated with the processing of a form has side
effects (for example, modification of a database or subscription to a
service), the method should be POST. (http://www.cs.tut.fi/~jkorpela/
forms/methods.html).

However, later I did not find any convinced arguments why it should
help (it can be that I just did not understand something).

So, I have decided not to go into the details of GET and POST methods
and just use POST. Is here any significant difference between GET and
POST which I should worry about (like security issues or something
else)? Or it is just question of convenience?

Use GET when your script is getting information to display to the user.
e.g. A product display get for product id=1, you want to GET the information.

Use POST when you are posting information back to the script to be manipulated
in some fashion.
e.g. Submitting a form with an email for subscription to a newsletter. You
want to POST the information to the script to be handled by a database of
some sort.

D.
--
Superman wears Paul O'Connell pyjamas.

[Jerry Stuckle]

Manuel Lemos wrote:

Hello,

on 01/15/2008 12:19 AM Kurda Yon said the following:

>Hi,

I have to decide which form-method I should use (GET or POST). I found
the following recomendation:
If the service associated with the processing of a form has side
effects (for example, modification of a database or subscription to a
service), the method should be POST. (http://www.cs.tut.fi/~jkorpela/
forms/methods.html).

However, later I did not find any convinced arguments why it should
help (it can be that I just did not understand something).

So, I have decided not to go into the details of GET and POST methods
and just use POST. Is here any significant difference between GET and
POST which I should worry about (like security issues or something
else)? Or it is just question of convenience?

I think with GET you are limited to sending with no more than 255
characters. Above that the browser may chop your submission URL.

Incorrect. There is no standard, and different browsers handle things
differently. I've seen people pass 1K in a GET request - although I
definitely do NOT recommend it! :-)

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attglobal.net
==================

[Jerry Stuckle]

Kurda Yon wrote:

Hi,

I have to decide which form-method I should use (GET or POST). I found
the following recomendation:
If the service associated with the processing of a form has side
effects (for example, modification of a database or subscription to a
service), the method should be POST. (http://www.cs.tut.fi/~jkorpela/
forms/methods.html).

However, later I did not find any convinced arguments why it should
help (it can be that I just did not understand something).

So, I have decided not to go into the details of GET and POST methods
and just use POST. Is here any significant difference between GET and
POST which I should worry about (like security issues or something
else)? Or it is just question of convenience?

Another consideration - GET URLs can be bookmarked. POST URLs cannot.
So, for instance, if you're displaying a restaurant from a list, GET
would be good so the user could bookmark it. But if you're adding data
to a database, you wouldn't want them to add it every time they visit
the page so you'd want to use POST.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attglobal.net
==================

[John Dunlop]

Kurda Yon:

I have to decide which form-method I should use (GET or POST).

http://www.w3.org/2001/tag/doc/whenToUseGet.html

--
Jock

[Toby A Inkster]

Jerry Stuckle wrote:

Manuel Lemos wrote:

>I think with GET you are limited to sending with no more than 255
characters. Above that the browser may chop your submission URL.

Incorrect. There is no standard, and different browsers handle things
differently. I've seen people pass 1K in a GET request - although I
definitely do NOT recommend it! :-)

Although browsers, proxies and servers are free to support URLs of any
length, HTTP/1.1 [1] does explicitly mention 255 characters as the length
above which people ought to exercise caution.

____
1. Hypertext Transfer Protocol -- HTTP/1.1
<http://www.ietf.org/rfc/rfc2616.txt>,
R Fielding, J Gettys et al, 1999.
3.2.1: General Syntax.

--
Toby A Inkster BSc (Hons) ARCS
[Geek of HTML/SQL/Perl/PHP/Python/Apache/Linux]
[OS: Linux 2.6.17.14-mm-desktop-9mdvsmp, up 15 days, 23:42.]

GPS & Cameras
http://tobyinkster.co.uk/blog/2008/01/14/gps-cameras/

[Toby A Inkster]

Jerry Stuckle wrote:

Another consideration - GET URLs can be bookmarked. POST URLs cannot.
So, for instance, if you're displaying a restaurant from a list, GET
would be good so the user could bookmark it. But if you're adding data
to a database, you wouldn't want them to add it every time they visit
the page so you'd want to use POST.

And another: Login forms should normally be POSTed, so as not to reveal
the password in the browser's address bar.

One more: for file uploads, you'll need to POST.

--
Toby A Inkster BSc (Hons) ARCS
[Geek of HTML/SQL/Perl/PHP/Python/Apache/Linux]
[OS: Linux 2.6.17.14-mm-desktop-9mdvsmp, up 15 days, 23:49.]

GPS & Cameras
http://tobyinkster.co.uk/blog/2008/01/14/gps-cameras/

[The Natural Philosopher]

David Gillen wrote:

On Tue, 15 Jan 2008 Kurda Yon <ku******@yahoo.comwrote:

>Hi,

I have to decide which form-method I should use (GET or POST). I found
the following recomendation:
If the service associated with the processing of a form has side
effects (for example, modification of a database or subscription to a
service), the method should be POST. (http://www.cs.tut.fi/~jkorpela/
forms/methods.html).

However, later I did not find any convinced arguments why it should
help (it can be that I just did not understand something).

So, I have decided not to go into the details of GET and POST methods
and just use POST. Is here any significant difference between GET and
POST which I should worry about (like security issues or something
else)? Or it is just question of convenience?

Use GET when your script is getting information to display to the user.
e.g. A product display get for product id=1, you want to GET the information.

Use POST when you are posting information back to the script to be manipulated
in some fashion.
e.g. Submitting a form with an email for subscription to a newsletter. You
want to POST the information to the script to be handled by a database of
some sort.

D.

Either method works: a GET method is slightly insecure, in that an
average idiots can fake a URL and maybe get where they shouldn't: Its
harder to do with POST. There you would have to make up a web page form
to submit with POST to the URL you were trying to screw with.

Get is nice because you can use links to get to a GET enabled page..no
need to carate a form or anything.

I tend too use get for simple indexing into a page of data, and POST to
do the real work. Many of my scripts accept both.