Bug ID 1073973: Gateway HTTP/2, response payload intermittently not forwarded to client.

Last Modified: May 29, 2024

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

Known Affected Versions:
16.1.0, 16.1.1, 16.1.2, 16.1.2.1

Fixed In:
17.0.0, 16.1.2.2

Opened: Jan 19, 2022

Severity: 3-Major

Symptoms

Some HTTP/2 requests through a Gateway HTTP2 (HTTP2 clientside/HTTP1 serverside, no MRF) stall, with: - the BIG-IP receives a request and forwards it to the server - the server responds with both headers and response body - the BIG-IP forwards the response headers back to the client - the BIG-IP does not forward the response body to the client

Impact

HTTP response body is not forwarded to the client from the BIG-IP system.

Conditions

-- BIG-IP virtual server configured with an HTTP/2 profile on both the client side and server side -- A high number of HTTP/2 requests traverse the HTTP/2 connection

Workaround

N/A

Fix Information

N/A

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips