Skip to content

Conversation

@rauladorean
Copy link

Hi,

We ran into an issue with the User-Agent rules order.

The block rule on Octopus User-Agent is matched before L491 any good User-Agents can match L848. Considering that the bad User-Agents are matched before the Good ones, I propose that we move the bad User-Agents after the good and rate limited ones.

In the process, I also added Revolut-Octopus as a good User-Agent.

If a request User-Agent will match a Bad User-Agents, the Good User-Agents are never checked.
Sure, you can use bots.d/blacklist-user-agents.conf, but for something generic that you want to whitelist on all servers I consider this approach simpler.
Revolut payment processing uses "Revolut-Octopus/1.0" User-Agent to send callbacks.
These requests are blocked by the "Octopus" bad User-Agent rule.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant