Bug ID 2130729: HTTP::respond not working properly with HTTP3/quic - content not sent

Last Modified: Oct 17, 2025

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

Known Affected Versions:
16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 16.1.6, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.5.1, 17.5.1.2, 17.5.1.3

Opened: Oct 09, 2025

Severity: 3-Major

Symptoms

irule for http/3 virtual server with HTTP::respond that includes content will not send the content

Impact

Not able to use HTTP::respond with content

Conditions

The header sent to the client does indicate content with a content-length above 0 * Request completely sent off < HTTP/3 200 < content-type: text/html < server: BIG-IP < content-length: 179 But no content is sent and the connection is terminated abnormally.

Workaround

None

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips