another one to deny

[littleman]

IP 209.73.228.163
UA trademarktracker.com

As you could see it left a nice little ad in my logS via UA.

[Key_Master]

I recommend banning the entire webclipping.com IP range.

Webclipping.com (NETBLK-WEBCLIP-209-208-242) WEBCLIP-209-208-242
209.73.228.160 - 209.73.228.175

[jdMorgan]

Key_Master,

Who are these Webclipping guys, and what do they do (from our viewpoint, not theirs)?

What is the most efficient way to bloack a range that does not fall on "nice" class boundaries like these?

209.73.228.160 - 209.73.228.175

^209\.73\.228\.1[6-7][0-9] gets close, and
^209\.73\.228\.1(6[0-9]¦7[0-5]) gets it all, but is there a "better" - or more readable and maintainable way?

Thanks,

Jim

[Key_Master]

At the very least, they're bandwidth parasites. At worst, they're using your content against you by aiding your competitors. Check out their Web site for more details. IMO, all snoop bots should be banned.

I use:

# Webclipping.com
^209\.73\.228\.16[0-9]$
^209\.73\.228\.17[0-5]$

[jdMorgan]

Key_Master,

Thanks for the reply. I'm always trying to find the most efficient way to ban the worst offenders, thus my interest in getting it down to a one-liner.

We're so low-profile (so far) that I rarely get a revisit from anyone I've added to the badbot list. In most cases, I'm playing catch-up. The main exceptions so far have been badbots I've banned based on others' lists I found here. I'm grateful for that, 'cause it probably saved me a bunch of spam e-mail and considerable bandwidth.

Jim

[Key_Master]

I see why you would want to keep it a one liner. I don't 'cuz I get blurry eyed when I look at them. ;)

Like this one:

# Nameprotect.com
SetEnvIf Remote_Addr ^12\.40\.85\. ban
SetEnvIf Remote_Addr ^12\.148\.196\.(12[8-9]¦1[3-9][0-9]¦2[0-5][0-9])$ ban

[jdMorgan]

Ouch!

I see what you mean... :)

I'm just trying to keep my list short and compact to avoid making Apache read through the encylopdedia brittanica on every file access. But your example shows clearly how "too much" compression might affect maintainability.

Thanks,
Jim