Forum Discussion
hooleylist
Dec 20, 2011Cirrostratus
Hi James,
Only one ASM policy will be used by default based on which HTTP class matches the request. If you want to disable web scraping protection for specific geo-locales, you could create two copies of the policy with web scraping disabled on one. Then using an iRule with whereis to check the client IP, you could call HTTP::class to select the correct class and ASM policy.
I see a lot more requests these days for making GeoIP based decisions. You could open a request for enhancement to add logic to the HTTP class filters to match a class based on GeoIP data. You could also ask for a new feature to disable ASM policy enforcement of specific validations by client IP or GeoIP data. If you do this, could you reply back with what you hear from Support?
Aaron