Last Modified: Jul 12, 2023
BIG-IP APM, ASM, LTM, SWG
Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 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, 13.1.1, 14.0.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 14.0.1, 188.8.131.52
Opened: Jul 09, 2018 Severity: 3-Major
When ramcache serves a 206 Partial Content response from cache, the Content-Range header repeats the name: Content-Range: Content-Range: bytes 0-5/28
The client may mishandle the response, as the Content-Range header is malformed. This may cause additional traffic as the client may retrieve the entire document in a subsequent request due to the malformed response.
Request from client for partial document (Range header) against a virtual server with a web-acceleration profile having no applications (ramcache), where the requested document is present in ramcache.
Remove the duplicate portion of the Content-Range header using an iRule at HTTP_RESPONSE_RELEASE time.
The Content-Range header is now correctly formed for 206 Partial Content responses served from ramcache.