Last Modified: Mar 17, 2021
See more info
Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 11.6.4, 11.6.5, 220.127.116.11, 18.104.22.168, 22.214.171.124, 12.0.0, 12.0.0 HF1, 12.0.0 HF2
12.1.0, 12.0.0 HF3
Opened: Feb 19, 2016
When ACCESS::disable command is used in an iRule along with a Category Lookup agent in a per-request policy, the HTTP request we be incorrectly dropped and the connection reset. This error condition may also occur with other per-request policy agents.
The HTTP request will be dropped or the HTTP connection will stall and timeout.
APM deployed with a Per-Request policy using a Category-Lookup agent and an iRule which issues the ACCESS::disable command associated on the same virtual server.
When ACCESS::disable is used in an iRule on a virtual server with an Access Profile and Per-Request Policy assigned, BIG-IP APM will not run the Per-Request policy.