Bug ID 539809: Debug header may show misleading information when Symmetric deployment is configured

Last Modified: Sep 13, 2023

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

Known Affected Versions:
12.1.0, 12.1.1, 12.1.2, 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, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 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.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, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 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

Opened: Aug 13, 2015

Severity: 4-Minor

Symptoms

X-WA-Info header shows that a response was served from a remote BIG-IP while it was served from the central BIG-IP.

Impact

Information is misleading and may cause confusion in interpretation of http request/response flow. It requires to match the debug header to BIG-IP configuration to extract correct information. If the traffic capture is separated from the configuration snapshot, it may increase a chance of a mistake during analysis.

Conditions

BIG-IP has to be configured as a central device in AAM Symmetric Deployment, a policy node allows caching of a compressed response. After the response is cached, X-WA-Info header shows that the response was served from a remote BIG-IP for the consequent requests.

Workaround

While this information is misleading, it still contains useful information which can be extracted and confirmed with a configuration snapshot.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips