In Photos dot Org » web bot http://inphotos.org no photoshopped images here Thu, 26 Jan 2012 22:21:17 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 Google Photos Screensaver 2.0 http://inphotos.org/2008/04/11/google-photos-screensaver-20/ http://inphotos.org/2008/04/11/google-photos-screensaver-20/#comments Fri, 11 Apr 2008 06:33:59 +0000 Donncha O Caoimh http://inphotos.org/?p=1295 Check your web server logs. The Google Photos Screensaver 2.0 web bot does not respect robots.txt rules. It tripped over my tarpit a few days ago and I just noticed it hitting the same url again this morning. It’s banned now.

The strange thing is, I saw two requests from this user agent a few minutes ago. One from 66.249.85.129 which is a Gooogle IP, and another from 117.193.129.58 which looks like an Indian IP.

Which one tripped over my tarpit? The Google IP address, 66.249.85.129 did.

If you want to ban “Google Photos Screensaver 2.0″, add these lines to the .htaccess in your root directory (presuming you have mod_rewrite enabled of course!)

RewriteCond %{HTTP_USER_AGENT} .*Google Photos Screensaver 2.0.*
RewriteRule .* - [F,L]

I also ban a number of other user agents. This could could be merged into a few less lines but this makes it easy to add new lines quickly:

RewriteCond %{HTTP_USER_AGENT} Microsoft URL Control.*
RewriteRule .* - [F,L]
RewriteCond %{HTTP_USER_AGENT} WebAlta Crawler/2.0.*
RewriteRule .* - [F,L]
RewriteCond %{HTTP_USER_AGENT} .*larbin.*
RewriteRule .* - [F,L]
RewriteCond %{HTTP_USER_AGENT} Python-urllib.*
RewriteRule .* - [F,L]
RewriteCond %{HTTP_USER_AGENT} libwww-perl.*
RewriteRule .* - [F,L]
RewriteCond %{HTTP_USER_AGENT} .*Indy Library.*
RewriteRule .* - [F,L]
RewriteCond %{HTTP_USER_AGENT} .*Jakarta Commons-HttpClient.*
RewriteRule .* - [F,L]

Related Posts

]]> http://inphotos.org/2008/04/11/google-photos-screensaver-20/feed/ 3