I admit that there are very few use cases, but there is one already mentioned by sergerod: searches. Have a look at google's search box.
On 8/14/07, Chris Hartjes <[EMAIL PROTECTED]> wrote: > > On 8/14/07, teemow <[EMAIL PROTECTED]> wrote: > > > > What's the security difference between GET and POST. This has nothing > > to do with security. > > My fault for not fully explaining myself. You are correct that GET > and POST have nothing to do with security. > > > Semantically and for the sake of REST: If you use a form to retrieve > > something from your application, it may even more make sense to use a > > GET. On the other hand if you change something (add/update) with your > > form you should definitely use a POST. > > Interesting advice, but I've made it a personal practice to never > create a form that uses GET. I'd love to hear a good, constructive > reason for when a GET is preferred to a POST when creating a form that > submits information somewhere. I don't see any reason to use GET for > a form. > > -- > Chris Hartjes > Senior Developer > Cake Development Corporation > > My motto for 2007: "Just build it, damnit!" > > @TheBallpark - http://www.littlehart.net/attheballpark > @TheKeyboard - http://www.littlehart.net/atthekeyboard > > > > -- Timo Derstappen http://teemow.com mailto:[EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
