Forum Discussion
Ashwin_Venkat
Jun 21, 2017Employee
The ability to disable/enable attack signatures on a per-URL basis was introduced as a feature only in v13. Therefore, in v13 and above, you can create the URL as an Allowed URL (Explicit or Wildcard) and then configure the Overridden Security Policy settings within the Attack Signature tab for that URL.
In all versions prior to that, you can only make this exception on the parameter level or else it'll need to be done globally for that policy. One other option, for these pre-13.x versions, would be to use the ASM::unblock iRule event.
These two links gives more insight regarding these iRule events:
https://devcentral.f5.com/wiki/iRules.ASM__unblock.ashx https://devcentral.f5.com/wiki/irules.asm__violation_data.ashx