Loading...
Loading...
A configuration option is missing for the unparseable request content subviolation override.
It is not possible to configure an override for this subviolation on a microservice.
The option is missing in the UI and REST.
An iRule can be used to mitigate this condition. The specific iRule will be different according to the use case, the following is an example (psaudo code): when ASM_REQUEST_DONE { if {[ASM::microservice] eq "/foo/*a/"} { if { [HTTP::uri] length > X} #trigger ASM custom violation }
None
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.