|
|
Posted by The Natural Philosopher on 11/12/87 12:00
David Gillen wrote:
> On Tue, 15 Jan 2008 Kurda Yon <kurdayon@yahoo.com> 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?
>>
> 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.
Navigation:
[Reply to this message]
|