There has to be a way to permanently whitelist IP's. I've read through past discussions on this and have come to the understanding that you do not want to offer this as a standard feature. At the same time this sort of control should be in the hands of the webmaster, not the application.

Here's why:

I installed this module on our main site as I have been using honeypot for years and trust its reliability. One of the things we do is use xml pages to feed content to what we call our micro-site. This site has a different IP than the main site. Rackspace, our host, uses a series of IP's to serve these feeds. These IP's are not the same as either of our web sites. This module systematically greylisted all of the IP's used by Rackspace to serve these feeds until our micro-site began to serve up blank pages as all of the available IP's used by Rackspace had been blocked.
As there was no way to permanently whitelist IP's I had to disable this module and go back to the old method of going through the access logs every day and checking for bad IP's. I had hoped to escape this tyranny with http:BL but have found that http:BL is even more draconian than I am.

It doesn't seem to be a great task of programming to add a permanent whitelisting capability to this module. As I am not in the habit of hacking other's modules I am putting this on your plate. Other than the aforementioned issue this module could be a real time saver for webmasters like myself. Thanks for listening.

Comments

jj’s picture

Please close. I just had an epiphany. I didn't realize that the access settings would allow me to whitelist these IP's.

bryrock’s picture

Status: Active » Closed (works as designed)