Bug ID 936061: Variable session.user.agent missing for Edge Client & F5 Access clients

Last Modified: Feb 29, 2024

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

Known Affected Versions:
12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5

Fixed In:
17.0.0, 16.1.4, 15.1.9

Opened: Aug 13, 2020

Severity: 4-Minor

Symptoms

When connecting with Edge Client & F5 Access clients the BIG-IP APM session variable session.user.agent is missing from APM sessions.

Impact

Session variable session.user.agent cannot be used for BIG-IP APM Access Policy logic flows

Conditions

BIG-IP APM Edge Client & F5 Access clients

Workaround

An iRule can be used to generate a like 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

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips