Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP APM
Known Affected Versions:
11.0.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.5.1 HF1, 11.6.1 HF1, 11.5.1 HF2, 11.6.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.5.2 HF1, 11.6.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0
Fixed In:
11.5.1, 11.5.0 HF1, 11.4.1 HF4, 11.3.0 HF9, 11.2.1 HF11
Opened: Jan 15, 2014 Severity: 3-Major Related Article:
K15181
An iRule that attempts to get session data in the ACCESS_SESSION_CLOSED event will always see empty values.
An iRule that depends on being able to manipulate session data during the ACCESSS_SESSION_CLOSED event will fail to find the data.
This issue was a side-effect of a fix to a different issue. This problem will occur for all iRules that attempt to get session data in the ACCESS_SESSION_CLOSED event.
There is no workaround available.
Session variables have been made available during the ACCESS_SESSION_CLOSED event. As a side effect, session variables are still available even after issuing the "ACCESS::session remove" command, because the actual removal is deferred until after the current iRule completes. However, it is considered an error to access that data outside of the ACCESS_SESSION_CLOSED event.