Disable web scraping detection per geolocation?

Hoolio and Mike, thank you very much for the responses. Firstly, can I ask what the best way is to request an enhancement, should i raise a websupport case?

 

 

Regarding the HTTP classes, is it the case that only one http class can fire? As i was attempting to have two classes, both with identical configuration (that is, both have the defaults apart from asm enabled. Neither is more specific than the other). In this scenario, it was always the http class at the top that fired, the one below it never seemed to fire, although i would have expected the asm to work down them in order, only the top one fired, and if the request passed through that class, it was then passed to ltm without going to the second class.

 

 

 

If I am to have two separate classes, how can i have two policies and keep them in sync, apart from having web scraping enabled or disabled. Is this possible? We still want to look for various attack signatures even from trusted countries, we just want to disable the web scraping part. If we are to have two separate policies, then this means twice the admin work to keep the policies up to date, which won't be possible for us as a team. We really need just one policy to administer, but to disable web scraping for trusted countries. It's a tough one!