Last Modified: Jul 12, 2023
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1
Fixed In:
14.1.0
Opened: Jan 08, 2018 Severity: 3-Major
The HTTP/2 protocol multiplexes multiple streams in a single connection. If a stream aborts, the connection might not. The HTTP/2 protocol condenses the reset cause into a single 4-byte integer, which is not enough to determine the real reason for the stream aborting. This makes debugging issues with HTTP/2 difficult.
The debugging of virtual servers that use HTTP/2 is more difficult.
A HTTP/2 stream aborts for any reason.
There is no workaround at this time.
When HTTP/2 streams abort, the reset cause may be recorded in the stats, if desired. This is configured using the normal rstcause configuration mechanisms. A BigDB var has been added: Tmm.HTTP2.sendrstwhy. If set to 'true' and an HTTP/2 stream aborts, the BIG-IP system sends an HTTP/2 frame containing reset cause information. The frame is of type '0xf5' = 245.