Last Modified: Jan 20, 2023
See more info
Known Affected Versions:
14.1.0, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 14.1.2, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 14.1.3, 184.108.40.206, 14.1.4, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 14.1.5, 220.127.116.11, 18.104.22.168, 22.214.171.124
Opened: Aug 09, 2022
- The BIG-IP system only successfully responds to the first HTTP request per TCP connection. - Any following HTTP request is not responded, the TCP connection is reset, and the BIG-IP system logs an error similar to the following example to the /var/log/ltm file: Jul 11 18:03:10 bigip.local err tmm: 01220001:3: TCL error: /Common/my-rule <HTTP_REQUEST_DATA> - Expired (line 1) invoked from within "HTTP::payload"
Inability to pass more than one HTTP request per TCP connection. Applications may display poor performance as a result or not function at all.
- The inbound HTTP requests carry a payload and use HTTP chunking as the transfer encoding. - The standard (tcp+http) virtual server on the BIG-IP system uses an iRule that employs the HTTP::collect + HTTP::payload + HTTP::respond commands.
If you control the HTTP clients and can change their behavior, avoid using HTTP chunking there. Alternatively, rewrite the iRule so that HTTP::collect and HTTP::payload are not invoked. Note: This issue does not affect versions 15.0.0 and later. Upgrading the BIG-IP system to a recent software version is recommended.