By HS on

I ban spambots using Drupal's Access Rules (admin/user/rules/add) but the list has gotten fairly long (thousands of IPs).

I have two questions,

1. Is it better to remove all this data from my database and block these IPs in .htaccess?

2. Is there a performance hit if several of these banned IPs visit each time and I was using Access Rules to block access? There is a query to the DB each time a banned IP accesses the site, right?

Thanks in advance!

-HS

Comments

ayesh’s picture

ayesh commented

I'd use a rather different way to do so.
Editing .htaccess for each and everytime is not a very good idea - probably you have experience already.
Access Rules doesn't prevent users from requesting static files. I think a dfferent way, like HTMLBL should do this efficiently.

also, I'd suggest to not tag posts to all Drupal versions unless they are really related to the version. I mean... an API that exists in specific versions ?

What's new and changing in PHP 8.4

HS’s picture

HS commented

Thank you for the reply. I removed the tags.

So, Access Rules or .htaccess? I do realise the latter is cumbersome but what I'm trying to determine is if it's worth the effort and time.

ayesh’s picture

ayesh commented

.htaccess blocking affects whenever the user connect to your server. So blocking both static and Drupal-generated pages.
If the list goes high, I think Access Rules should work better than .htaccess.
However, in Access Rules, Drupal gets invoked. So brute-force like attacks, try to use a server side method.

What's new and changing in PHP 8.4

HS’s picture

HS commented

Thanks!