Bug ID 1000561: HTTP chunked encoding markers incorrectly passed to HTTP/2 client-side

Last Modified: Jun 01, 2024

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

Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 17.0.0, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3

Fixed In:
17.1.1, 16.1.4, 15.1.9

Opened: Mar 09, 2021

Severity: 3-Major

Symptoms

HTTP/2 virtual servers pass the chunk size bytes from the server-side (HTTP/1.1) to the client-side (HTTP/2) when OneConnect and request-logging profiles are applied. This results in a malformed HTTP response.

Impact

The HTTP response passed to the client-side includes chunk size header values when it should not, resulting in a malformed HTTP response.

Conditions

-- BIG-IP configured with a HTTP/2 virtual server using OneConnect and request-logging profiles. -- The pool member sends a chunked response.

Workaround

Change HTTP response-chunking to either 'unchunk' or 'rechunk' in the HTTP profile for the virtual server.

Fix Information

The HTTP response egressing the client-side no longer includes chunk size bytes.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips