Bug ID 2201813: BIG-IP enforces maximum concurrent streams limit immediately over HTTP/2 connection

Last Modified: Oct 08, 2026

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

Known Affected Versions:
17.5.1, 17.5.1.2, 17.5.1.3, 17.5.1.4, 17.5.1.5, 17.5.1.6, 17.5.1.8, 17.5.1.9

Fixed In:
21.1.0, 21.0.0.2

Opened: Jan 14, 2026

Severity: 3-Major

Symptoms

BIG-IP negotiates a number of concurrent streams over a connection per requirement. It enforces this limitation once the protocol is agreed and the first frame is issued.

Impact

The client may send more requests than the limit set over the established connection, causing the system to reset the extra streams. If protection is enabled, it may result in the connection being shut down by the system.

Conditions

-- Virtual server with a http2 profile. -- A client connects to the virtual server and negotiates or starts HTTP/2 connection.

Workaround

None.

Fix Information

The system no longer sends reset frames when the number of streams exceeds the configured limit until acknowledgment is received to designate the honoring of the limit by the peer.

Behavior Change

Concurrent streams are treated as unlimited until the peer’s SETTINGS/ACK frame arrives or a 1-second timeout expires, after which the configured limit is enforced. Until then, stream-specific frames are queued with a soft limit allowing up to 128 frames and 128 KB of frame-body data.

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips