|
|
Posted by xkorakidis on 09/29/33 11:32
That's right Curt,
this is the reason I characterised sending parameters via url not safe!
But in case of selecting data, I think there is no problem to send data
via url, right?
anyway, I found more simple using POST in any case because I have
already used that and works, so I prefer POST...
Thanks!
Curt Zirzow wrote:
> On Sun, Nov 20, 2005 at 04:12:05PM +1300, Jasper Bryant-Greene wrote:
>>xkorakidis wrote:
>>>Webmaster, thanks very much but I think it would be safer to do that by
>>>post, not by get. Furthermore, if I use indivudual files
>>The difference between POST and GET lies in the semantics -- POST
>>represents something changing on the server, e.g. updating a database
>>field, and allows the browser to warn the user if they try to refresh.
>>GET represents nothing of importance changing on the server, e.g.
>>performing a search on the database, and can safely be repeated.
>
> Another good reason to use POST to modify data, consider the link:
>
> http://example.com/posts.php?postid=1&action=delete
>
> If googlebot comes across your page containing a list of all your
> posts, with a link like that, you just might wake up one morning
> wondering why all your posts are gone.
>
> Curt.
Navigation:
[Reply to this message]
|