Bug ID 1538689: QUIC connections from the Chrome browser does not upgrade to HTTP/3

Last Modified: Jun 11, 2024

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

Known Affected Versions:
16.1.4.1, 16.1.4.2, 16.1.4.3

Opened: Feb 16, 2024

Severity: 3-Major

Symptoms

When virtual server in BIG-IP is configured to support Quick UDP Internet Connections (QUIC) protocol, a connection from client to a server which supports QUIC must be upgraded to HTTP/3. But, connections coming from the Chrome client continue as HTTP/2 instead of HTTP/3.

Impact

Unable to establish a QUIC connection with the server.

Conditions

- Connection must be initiated from the Chrome browser. - The server must support HTTP/3 or QUIC. - The TLS 1.3 0-RTT feature is disabled.

Workaround

Enabling the TLS 1.3 0-RTT feature allows the connection to continue in HTTP/3.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips