On Thu, Jan 22, 2009 at 5:35 PM, Trevor Phillips <[email protected]>wrote:
> On Thu, Jan 22, 2009 at 3:12 PM, Toby Corkindale > <[email protected]> wrote: > > > > But what happens when your site gets spidered by a search engine, that > > follows all links? > > > > Whoops. > > > > There's a good reason state-modification-actions should be POST (or > rather, > > non-GET, if you want to go with PUT, DELETE, etc) > > Surely such an action would be behind some form of authentication, > ergo blocking any random web crawler? An app that allowed you to > delete records with no security checks has bigger issues. ^_^ Except, what if the crawler is inside the user's browser? Google's Web Accelerator supposedly caused a lot of grief in 2005 when it started pre-fetching non-idempotent GET requests for unsuspecting users.. Patrick Donelan http://patspam.com
_______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
