Bug ID 1024761: HTTP adds Transfer-Encoding and terminating chunk to responses that cannot have a body

Last Modified: May 29, 2024

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

Known Affected Versions:
15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2

Fixed In:
17.0.0,, 15.1.5

Opened: Jun 10, 2021

Severity: 4-Minor


When rechunking is requested, HTTP responses with methods or status codes indicating that no body be present (like HEAD or 304) are receiving a Transfer-Encoding header and a terminating chunk. These responses should not have a body of any sort.


HTTP clients are unable to connect.


HTTP virtual server with rewrite profile present with the server that does HTTP caching.


Remove the rewrite profile. Possibly change http profile response-chunking from sustain to unchunk. This resolves the issue for the 304, but means that all other requests are changed from either chunking or unchunked with Content-Length header to unchunked without Content-Length and with "Connection: Close".

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips