Symptoms

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.

Impact

Browser fail to process responses.

Conditions

Responses that contain the same header (with possibly different values) more than once.

Workaround

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.

Fix Information

The http/2 protocol handling now correctly encodes repeated headers.

Behavior Change