Bug ID 2331445: HTTP/2 Connection May Stall When a Single Response (or request) Exceeds The Per-pass Egress Write Limit

Last Modified: Jul 10, 2026

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

Known Affected Versions:
17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.1.3.1, 17.1.3.2, 17.5.1, 17.5.1.2, 17.5.1.3, 17.5.1.4, 17.5.1.5, 17.5.1.6

Opened: Jun 10, 2026

Severity: 3-Major

Symptoms

HTTP/2 traffic can stop mid-transfer. The connection delivers approximately 16 KB of payload and then goes idle until it is closed by an idle timeout

Impact

Stalled HTTP/2 streams; the client or server peer eventually times out

Conditions

- A single HTTP/2 message produces more queued DATA frames in one egress pass than the HTTP/2 profile's per-pass write size (default 16 KB) - No further application-layer writes follow on the affected stream(s) (typical for a completed response or a fully buffered request body)

Workaround

A workaround is possible by having the frame-size lower than ltm profile http2 http2_New { app-service none defaults-from Profile_http2 frame-size 8191 # Lower than write-size 8192 header-table-size 65536 write-size 8192 }

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips