Forum Discussion
Disable web scraping detection per geolocation?
1) Disabled the web scraping part of the policy on our default ASM policy/class, but still have it looking for attack signatures.
2) created a new policy / class with ONLY web scraping detection enabled, everything else it does not look for.
I've then applied both classes to a VIP, both classes are default apart from "security enabled". This is my first stumbling block - only the top class seems to fire. If you get through the policy for the class that is on top then it lets you through without going down to the second class.
Is this how it should behave, and am i going down the wrong track?
Thanks
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com