Last Modified: Oct 06, 2020
See more info
Known Affected Versions:
11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3
12.0.0, 11.6.0 HF4, 11.5.2 HF1
Opened: Jul 01, 2014
Related AskF5 Article: K04393808
A wrong display of the request status (as a blocked request) for requests that were only alarmed.
A wrong display of the request status as if it is a blocked request when it was alarmed request.
Web scraping in alarm mode, ASM iRules in place.
This issue has no workaround at this time.
When web scraping mitigation configuration mode is set to Alarm (log) and there is an ASM iRule, the iRule no longer displays requests as being blocked when they are actually logged and not blocked.