By default the regex match limit is set to 30k cpu cycles in the WAF profile.
In some scenarios, HTTP request may be rejected or flagged by CRS rules with error "Processing aborted: operator Rx failed: regex execution limit exceeded, regex_match_limit=30000"
Example WAF log:
In order to resolve this error you would increase the regex match limit in the WAF profile. However, increasing the value does not resolve this issue.
Example:
Doubled valued - 60k
Doubled value - 120k
Doubled value - 240k
Affects Version(s): 22.1.7, 30.2.1, 30.2.2, 31.1.1
There was a recent change in the product where CRS rules have been decoupled from the WAF policy and virtual service, this affected how the CRS rules are processed leading to regex execution limit exceeded issue. This only affects CRS rules. Configured Pre-CRS and Post-CRS rules are proceed correctly and the regex_match_limit is honored.
This issue is still under review, while a permanent resolution is delivered, please apply the optional workaround(s):