In , we added a filter based on the User-Agent.
However, BadBehaviour continues to release updates based on IP ranges (using CIDR notation), i.e.,
We need to verify that our filter still works.
Maybe, this is a quick fix now that CIDR notation is supported? or maybe we don't really care since it is not an issue and maybe we should not trust badbehavior db anyway!
before adding any of the ip ranges used by badbehavior, we'll verify the netblock belongs to Google/Bing/etc
(In ) fixes #1948 - confirmed these are Microsoft assigned netblocks; should we incubate the BotTracker in #2391 to takeover the smartbot filtering?