Last Modified: Jul 18, 2026
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
11.6.0, 11.6.0 hf1, 11.6.0 hf2, 11.6.0 hf3, 11.6.0 hf4, 11.6.0 hf5, 11.6.0 hf6, 11.6.0 hf7, 11.6.0 hf8, 11.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 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
Fixed In:
12.0.0
Opened: Apr 03, 2015 Severity: 3-Major Related Article:
K17023
If a http/2 request, forwarded to an http/1.1, produces a response that has the same header occurring more than once, the http/2 response would be encoded incorrectly and can't be processed by the http/2 browser.
Browser fail to process responses.
Responses that contain the same header (with possibly different values) more than once.
For the set-cookie header there is no work-around because each cookie requires its own header. For other headers, an iRule could potentially be used to concatenate the values of repeated headers.
The http/2 protocol handling now correctly encodes repeated headers.