Last Modified: Oct 16, 2023
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
11.6.2 HF1, 11.3.0, 11.4.0, 11.4.1
Fixed In:
11.6.0, 11.5.1 HF5, 11.4.1 HF6
Opened: Mar 27, 2014 Severity: 3-Major
After ICAP modification is fully received by the BIP-IP system, the HTTP payload may be truncated before all of it reaches its destination.
Modified ICAP data returned to HTTP server or client is truncated.
Transmission of HTTP result after ICAP modification (request or response) is pushing back with flow-control so that there is delay between payload received from the ICAP server and its transmission to the HTTP server or client. On 11.3 and 11.4 the impact is much bigger due to bug 429994.
No real workaround. If possible, avoid conditions requiring flow-control pushback from HTTP destination.
BIG-IP delays closing the internal connection to the IVS after the final chuck of the ICAP response has been received, until all the payload has been transmitted to the HTTP destination.