Forum Moderators: open
On Feb 18 of this year, the Class C fetched some pages and I implemented multiple conditions based on both IP and UA. (I'm sure that it will require adjustment).
Thanks for the heads up.
You can also configure your server to refuse prefetch requests by returning a 403 HTTP response code for requests which include an "x-moz: prefetch" header.
[webaccelerator.google.com...]
I am not suggesting that doing this actually works.
...
[scholar.google.com...]
Admittedly, that was written in regards to browser prefetching of Google search results, but I don't see much distinction between that and Google Web Accelerator. Has anyone ran any thorough testing of GWA's reaction to 403 vs 404 response codes?
[edited by: Umbra at 7:51 pm (utc) on July 4, 2008]
Certainly Google's instructions for dealing with it are useless, so I ended up with:
SetEnvIfNoCase X-Forwarded-For .+ proxy=yes
SetEnvIfNoCase X-moz prefetch gwa=yes
RewriteCond %{ENV:gwa} yes
On most of my sites the ensuing rule feeds it a 403 and seems to work fine.
Actually trapping it brings further complications, but they are not insurmountable.
It's really only worth trapping it as an academic exercise though (unless you want to make a point) and if memory serves the technique above will stop other similar stupidities like the IE7Pro plugin.
...