Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP APM
Known Affected Versions:
11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 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
Opened: Jul 12, 2013 Severity: 3-Major Related Article:
K17570
As a result of this issue, you may encounter one or more of the following symptoms: -- When the virtual server HTTP profile processes content, it modifies the HTTP server header value to the custom value. -- When adding the BIG-IP APM access profile to the same virtual server, the HTTP header server value is not modified.
Content processed by the BIG-IP APM access profile does not apply the custom server agent name value.
This issue occurs when all of the following conditions are met: -- You configure an HTTP profile with a custom server-agent-name value. -- You configure an access profile to use the same virtual server that utilizes the HTTP profile.
Use an iRule similar to the following to change the server header: HTTP::header replace Server [<string>]
Responses sent from the renderer now contain the Server header value as it is configured in the server-agent-name in the HTTP profile. If an empty server-agent-name is configured in the HTTP profile, the Server header is deleted in the responses sent from the renderer. If the server-agent-name is not configured, the default value, the BIG-IP system, is used as Server header value.