Bug ID 686422: URI reported in alert may not contain the actual traffic URI

Last Modified: May 01, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP FPS(all modules)

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5

Fixed In:
14.0.0

Opened: Oct 01, 2017
Severity: 3-Major

Symptoms

URI reported in alert may not contain the actual traffic URI.

Impact

Request URI is not reported correctly. The reported URI will contain the configured URL instead of traffic URL. For example: -- A configured URL: /*. -- Traffic URI: /a/b/c?n=v. -- Reported URI: /*. -- Reported URI should be traffic URI: /a/b/c?n=v.

Conditions

The alert was triggered for a wildcard-configured URL.

Workaround

None.

Fix Information

FPS always normalizes traffic URI and reports that in the alert payload.

Behavior Change