Bug ID 469786: Web Scraping Mitigation: Display of request status when configuration includes an ASM iRule

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP ASM(all modules)

Known Affected Versions:
11.5.1 HF1, 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.1 HF10, 11.5.1 HF11, 11.6.2 HF1, 11.6.0, 11.6.1, 11.6.2, 11.6.3,,,,, 11.6.4, 11.6.5,,,, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.0 HF4, 11.5.2 HF1

Opened: Jul 01, 2014

Severity: 3-Major

Related 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.

Fix Information

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.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips