Define a different threshold for each rule

Created on 27 July 2025, 6 days ago

Problem/Motivation

For some regex rules, I want to block the IP address immediately because they are so sensitive that I am very sure that it is not a search engine bot or similar. For other regex rules, you can't be quite so sure, which is why a different threshold makes sense there.

Steps to reproduce

/admin/config/system/perimeter

Proposed resolution

To be able to define a different threshold for each regex. The maintainer probably knows best how this could be implemented most effectively in the settings form.

If this functionality can be integrated, it might also be possible to add exceptions for user agents and IP whitelists so that these can also be defined per regex in addition to global settings.

Feature request
Status

Active

Version

3.0

Component

Code

Created by

🇨🇭Switzerland handkerchief

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @handkerchief
  • 🇩🇰Denmark ressa Copenhagen

    There's a new https://www.drupal.org/project/ip_limiter module which might work?

    The IP Limiter module for Drupal allows you to limit the number of requests from a single IP address to specific paths on your site. This can help prevent abuse and reduce server load.

    Or if it doesn't have the feature you're looking for, perhaps it could be added?

  • 🇨🇭Switzerland handkerchief

    Hi ressa, thanks for your reply. I will look into it thanks. Am I correct in assuming that this feature request will definitely not be integrated into this module if you even recommend that the other module should extend it if it is missing? Just so I know.

  • 🇩🇰Denmark ressa Copenhagen

    Sorry, I should have made it clearer that I am just a regular user of this module, and have no idea if it's possible or not.

    But I think it wouldn't harm, if you made more or less the same feature request in the other project as well, and then connected the two issues, so that if it gets made in one, the other issue can be closed.

    Your idea is great, and I hope it will become possible, in one of them :)

Production build 0.71.5 2024