| Author |
Message |
sixonetonoffun Spouse Contemplates Divorce

Joined: Jan 02, 2003 Posts: 2499
|
Posted:
Sat Mar 27, 2010 7:22 am |
|
This is a very intuitive approach to blacklisting using mod rewrite along with other insights to bots ect...
|
|
|
|
 |
nuken RavenNuke(tm) Development Team

Joined: Mar 11, 2007 Posts: 1435 Location: North Carolina
|
Posted:
Sat Mar 27, 2010 7:50 am |
|
Very nice. I am trying it on my test site to see if it stops any of the hack/spam attempts. I get at least 20 a week from my test site. |
|
|
|
 |
webservant Worker


Joined: Feb 26, 2006 Posts: 199 Location: Springfield, MA
|
Posted:
Sat Mar 27, 2010 6:46 pm |
|
Very intense! Is anyone else trying this?
I'd love to just plop it in, but I don't want to kill any of the good bot traffic (e.g., Google).
What's the downside? |
|
|
|
 |
sixonetonoffun Spouse Contemplates Divorce

Joined: Jan 02, 2003 Posts: 2499
|
Posted:
Sun Mar 28, 2010 7:55 am |
|
I think it would be interesting but.. don't have a live environment to test on right now.
I had to use the split rewrite conditions posted in the comments section to get running.
Anyone using it should take the time to study the post at the end of the page there are some obvious fixes and tips to find triggers when users/crawlers with non standard UA's are blocked. ISP supplied browsers ect... are notorious for branding refers.
Using a redirect instead of forbidden might help to refine the code as users would be able to understand WTF is going on and contact the webmaster. |
|
|
|
 |
|
|
|
|