Bug ID 956025: HTTP profile response-chunking "unchunk" option does not remove Content-Length from response header

Last Modified: Oct 05, 2023

Affected Product(s):
BIG-IP All(all modules)

Known Affected Versions:,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,,, 15.1.9,, 15.1.10,, 16.0.0,, 16.0.1,,

Fixed In:

Opened: Oct 15, 2020

Severity: 4-Minor


When the HTTP profile response-chunking option is set to "unchunk", chunked responses will be unchunked and the Transfer-Encoding header is removed. If the server sends a chunked response with both Transfer-Encoding and Content-Length headers, Transfer-Encoding is removed but Content-Length is not. This causes the client to receive a response with an erroneous Content-Length header.


Malformed HTTP response received by client as length of response should be determined by closure of connection, not erroneous Content-Length header.


- HTTP virtual server with response-chunking set to "unchunk" - Server response with both Transfer-Encoding and Content-Length headers present


Implement iRule: at HTTP_RESPONSE time, remove the Content-Length header if the Transfer-Encoding header is also present.

Fix Information

HTTP now removes Content-Length header when unchunking responses.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips