The_Contractor - 12:05 pm on May 5, 2005 (gmt 0) As Brett stated it uses your browsers UA so it can't be blocked via UA string.
I completely agree with claus on this. You know how I mentioned about site ripping through a proxy - already saw it on a clients site as I'm sure they didn't prefetch over 1200 pages (at 0 seconds between pageviews/pages)... So this morning I am banning it from all sites I have control over instead of just a couple I was concerned with.
Has anyone been able to identify it via User Agent yet
I think the only way to block it is through the IP range of 22.214.171.124 - 126.96.36.199 via .htaccess . I send them to a custom 403 on another domain (the .net,.info etc of the same domain name) in which I added one of the reasons they may have been blocked was by using the Google's webaccelerator.
As Brett stated it uses your browsers UA so it can't be blocked via UA string.