You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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):
The text was updated successfully, but these errors were encountered: