POST vs GET

So I've been told I should edit all my firefox search engine plugin .xml files and replace all GET method commands with POST. Please explain why.

For search engines? I don't know why.

If you want to get data, use GET.

If you want to create/modify data, use POST.

If you want to perform search, then use GET.

If you want to get your query logged, use GET.

If you want to avoid/limit logging, use POST.

If you want to perform search, then use POST.

If you sincerely believe websites log GETs but not POSTs, use POST.

Gets are easier to change and thus more insecure

visibility of data is the enemy

&Admin=0
oh let's change that to &Admin=1

oh look at that

>>6
You're fucking retarded.
Everyone knows admin requests are specified by login=admin

The GET can be  bookmarked, so at least all context and/or  temporal stuff needs to go in the POST. Stuff needed to get the page working (that is not tbrowing an incomplete command/query  go in  the GET.

The GET can be  bookmarked, so at least all context and/or  temporal stuff needs to go in the POST. Stuff needed to get the page working (that is not tbrowing an incomplete command/query  go in  the GET.

>>3-kun is right. l2REST.

>>10
Like I give a shit about web bullshite.

It's not about logging, cretins. Google & co. log every query anyway, in a database, they don't need to fetch it from the httpd access logs.

It's about the referrer. Searching "enterprise programming" using GET will result in a [tt]search-engine.com/search?q=enterprise+programming[/tt] URL, which is passed to the site you go to as you click on one of the results, in the HTTP referrer record.

With a POST search, the site will only be passed [tt]search-engine.com/search?post=true[/tt], or whatever, so that the site will not be passed your search query as you click on the link.

jesus, none of you fucks know a goddamn thing about networking.

[tt]
enterprise programming
IHBT