Bug ID 745682: Failed to parse X-Forwarded-For header in HTTP requests

Last Modified: May 29, 2024

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

Known Affected Versions:
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.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.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

Fixed In:
15.0.0, 14.1.3.1, 13.1.3.6

Opened: Oct 02, 2018

Severity: 3-Major

Symptoms

Failed to parse X-Forwarded-For header. This results in failure when extracting proper values in DOSL7.

Impact

DOSL7 does not receive the proper values for X-Forwarded-For.

Conditions

-- 'Accept XFF' is enabled in HTTP profile. HTTP profile is added to the virtual server. -- Bot Defense profile is added to the virtual sever. -- HTTP request contains 'X-Forwarded-For' header.

Workaround

None.

Fix Information

DOSL7 now receives the correct value under these conditions.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips