Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
11.4.0, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6
Fixed In:
13.0.0
Opened: Nov 22, 2013 Severity: 3-Major
When an HTTP v1.1 request of response is modified by ICAP and the resulting message has no Content-Length header, it might not be chunked when forwarded to the receiving HTTP server or client.
An invalid HTTP v1.1 modified request or response could cause undefined behavior in the HTTP client or server, respectively. For example, the end of the content cannot be identified due to lack of either Content-Length or chunking.
-- HTTP profile. -- Either request-adapt or response-adapt profile. -- Modified HTTP v1.1 request/response has no body (and no content-length header).
None
When an HTTP v1.1 request of response is modified by ICAP and the resulting message has no Content-Length header, it is forwarded to the receiving HTTP server or client with a "Transfer-Encoding: chunked" header and the payload is chunked.