Bug ID 1042505: Session variable "session.user.agent" does not get populated for edge clients

Last Modified: Feb 29, 2024

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

Known Affected Versions:, 12.1.5,,,, 12.1.6,,,, 13.1.4,, 13.1.5,,,,,, 14.1.5,,,,,, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,,, 16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,,,,

Fixed In:
17.0.0, 16.1.4, 15.1.9

Opened: Aug 24, 2021

Severity: 3-Major


Access policy agents and iRules that depend on "session.user.agent" session variable fail to execute properly.


Any access policy agents that depend on this session variable will not be able to follow the rules.


Access polices have agents that depend on the value of session variable "session.user.agent" for its execution.


An iRule can be used to generate a session variable. For example: # This event fires once per session when ACCESS_SESSION_STARTED { log local0. "Setting User-Agent based on HTTP data - [HTTP::header User-Agent]" ACCESS::session data set session.custom.client.useragent [HTTP::header User-Agent] #Use this variable in the VPE to make some decision }

Fix Information

Fix now sets the session variable properly.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips