Hmmm. I thought the open proxy check was a bit intensive, thus doing it only when a comment is submitted is a good approach. But I’d be interested to hear from one of the programmers who has implemented proxy detection code… 😉
-d
Moderator
James Huff
(@macmanx)
Volunteer Moderator
Use Bad Behavior, it blocks a few open proxies:
http://www.ioerror.us/software/bad-behavior/
I thought Bad Behavior is for comment spam only. I will try it, thanks.
“it blocks a few open proxies”
where can we get to know what proxies are blocked by the script?
Moderator
James Huff
(@macmanx)
Volunteer Moderator
I thought Bad Behavior is for comment spam only.
Bad behavior blocks all bad behavior, including bots which post comment, trackback, and referrer spam, bots which harvest email addresses, bots which ignore robots.txt, and bots which blatantly attempt to waste your bandwidth.
where can we get to know what proxies are blocked by the script?
All of the blocked user agents (and proxies) are commented in the files listed here:
http://dev.wp-plugins.org/browser/bad-behavior/trunk/
The file which blocks most of the open proxies is:
http://dev.wp-plugins.org/file/bad-behavior/trunk/bad-behavior-http-headers.php
Most of the open proxies that I have seen use a lower-case via tag in their HTTP headers. No known legitimate user has used such a tag, so that rule takes care of most open proxies.
If you need more information on the plugin, I highly recommend contacting the developer. He is very helpful.
