>behavior. GWA *only* issues GET requests, and if an app >modifies >data based on a GET, then the app should be considered >broken.
Actually the problem goes deeper: GWA can crawl areas that normally can't be crawled, because they are behind logins. So GWS will hit pages that were never meant to be hit by bots - private pages. But pages that aren't meant for public consumption have different requirements: you design them more often for convenience than for "good HTTP behaviour". So you will find GET-with-sideeffects more often behind logins than before logins (because those with side-effects on GET will already be hit by public bots). GWA is a very bad idea, and it is done in a very bad way. I can't think of any other google project where they fucked up that often (the last one being to drop the header that designates that some request is done by GWA instead of the browser itself). Even if you code your app to expected HTTP behaviour, GWA itself isn't allways. And we can't code our apps to HTTP brokeness of other apps ... So especially because of it's problems it is an absolute valid request to know how to block it out of some web site. bye, Georg
