Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] UptimeRobot/2.0 #201

Open
CHILIKE opened this issue May 13, 2024 · 1 comment
Open

[BUG] UptimeRobot/2.0 #201

CHILIKE opened this issue May 13, 2024 · 1 comment

Comments

@CHILIKE
Copy link

CHILIKE commented May 13, 2024

Describe the bug
In the globalblacklist.conf list agent UptimeRobot/2.0 is marked as a good_bot, but the script identfy it as a bad bot.

To Reproduce
In the apache log all connection with this agent UptimeRobot/2.0 is with status code 403
It is possible that the slash is confusing (but even then it should not be detected as a bad robot, max neutral).
The UptimeRobot IP 216.144.248.28 is not blacklisted.

Expected behavior
Status code 403
216.144.248.28 - - [12/May/2024:10:05:06 +0200] "HEAD / HTTP/1.0" 403 737 "https://www.(sitedomain).com" "Mozilla/5.0+(compatible; UptimeRobot/2.0; http://www.uptimerobot.com/)"

Server (please complete the following information):

  • OS: Debian, Ubuntu
  • Apache Version 2.4
mitchellkrogza added a commit that referenced this issue May 13, 2024
UptimeRobot tests Ref #201
@mitchellkrogza
Copy link
Owner

mitchellkrogza commented May 13, 2024

Passes in the Apache 2.4 tests added
https://github.com/mitchellkrogza/apache-ultimate-bad-bot-blocker/actions/runs/9063798691/job/24900513414#step:7:48

GitHub
Apache Block Bad Bots, (Referer) Spam Referrer Blocker, Vulnerability Scanners, Malware, Adware, Ransomware, Malicious Sites, Wordpress Theme Detectors and Fail2Ban Jail for Repeat Offenders - Upda...

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

No branches or pull requests

2 participants