atom feed16 messages in ru.sysoev.nginxRe: Blocking by user agent if ip does...
FromSent OnAttachments
karabajaMay 31, 2011 11:49 am 
António P. P. AlmeidaMay 31, 2011 12:04 pm 
Alexandr GomoliakoMay 31, 2011 12:18 pm 
Igor SysoevMay 31, 2011 12:34 pm 
Alexandr GomoliakoMay 31, 2011 1:34 pm 
António P. P. AlmeidaMay 31, 2011 2:03 pm 
Alexandr GomoliakoMay 31, 2011 2:27 pm 
karabajaMay 31, 2011 3:00 pm 
António P. P. AlmeidaMay 31, 2011 3:25 pm 
António P. P. AlmeidaMay 31, 2011 3:31 pm 
karabajaMay 31, 2011 3:44 pm 
António P. P. AlmeidaMay 31, 2011 3:57 pm 
Igor SysoevJun 1, 2011 12:24 am 
Igor SysoevJun 1, 2011 12:27 am 
Hari HendaryantoJun 1, 2011 1:41 am 
Igor SysoevJun 1, 2011 1:47 am 
Subject:Re: Blocking by user agent if ip doesn't match
From:António P. P. Almeida (ap@perusio.net)
Date:May 31, 2011 3:57:16 pm
List:ru.sysoev.nginx

On 31 Mai 2011 23h44 WEST, ngin@nginx.us wrote:

Thanks Antonio, so far we've only had fake google bots so it seems fine as it is for now. But I'll apply those if there is any issue with Yahoo or some other spider being faked. I am assuming that other user agents are not affected by the current rule.

No the default value of $bots is 0. Only in the case of a UA string containing google (case insensitive) is the IP verified. Otherwise, since you dropped the line that matched the bad bots UA, all other bots are allowed.

This is a good approach for handling bots spoofing the UA string and also a cleaner way to block unwanted bots.

--- appa