Super Bot Fight Mode is currently not compatible with many environments as it breaks APIs and internal webservices.
Currently it’s either enabled for a whole zone or disabled.
We need a way to disable it for specific paths (using page rules I guess) that are expected to be consumed by bots on regular basis (like API gateways)
Right now having it only globally active or not active is a show stopper that forces many zones to keep it disabled
We got the same problem. Accidentally activated the “super bot fight” and crashed all api functions on our websites. The page rules offer a lot of things to disable for specific URLs - but not for this bot fight mode: any plans to integrate this?
I would like to suggest there should have an except list for the definitely automated on the Configure Super Bot Fight Mode.
As I have added some traffic is not a bot to accept them on the Firewall Rule, but when I turned it on definitely automated as blocked, It does also not work. this traffic is also blocked.
So, when we have some custom Rule on the Configure Super Bot Fight Mode, it should be really cool and will not block this traffic in the future.
I have do the same thing on the Firewall, but it does not working when I turn on the Definitely automated as blocked.
any progress on this, i have an iOS app that (i cant change) and connects to an internal service incorrectly marked as a bot. Crazy I have to disable bot protection for the whole domain.
only solution seems to move API endpoints to a free zone and then leave the frontend website on another zone