Last Modified: Jun 10, 2021
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
Opened: Mar 12, 2019
Reading an object from the BIG-IP system.
The client will wait for the BIG-IP to deliver the amount of data specified by the Content-Length header, but since the object was compressed, there isn't that much data to deliver.
The virtual server has both a web acceleration profile with an active application and the HTTP compression filter on it. When reading a compressible object from the web acceleration small object cache, the HTTP compression filter may compress the data, but not rewrite the Content-Length header.
You can use either of the following workarounds: -- Remove the HTTP compression filter from the virtual server. -- Mark objects smaller than 4,000 bytes as no-store.