Bug ID 473771: No URL path in the Browser Automation alert

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP FPS(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.5.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, 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

Opened: Jul 31, 2014

Severity: 3-Major

Symptoms

Vtoken alerts are sent without the protected URL path in alert payload. This impacts alerts analysis, since it is impossible to determine the origin URL of the alert.

Impact

No URL path in the Browser Automation alert. This makes vtoken alerts analysis difficult and more time consuming.

Conditions

1. Automatic transactions enabled on a URL. 2. Automatic transaction alert is generated.

Workaround

None.

Fix Information

Fixed the client_request_uri so there is now a URL path in the Browser Automation alert.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips