Last Modified: Sep 13, 2023
BIG-IP Install/Upgrade, LTM
Known Affected Versions:
15.0.0, 15.0.1, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 15.1.1, 15.1.2, 18.104.22.168, 15.1.3, 22.214.171.124, 15.1.4, 126.96.36.199, 15.1.5, 188.8.131.52, 15.1.6, 184.108.40.206, 15.1.7, 15.1.8, 220.127.116.11, 18.104.22.168, 15.1.9, 22.214.171.124, 15.1.10
Opened: Apr 15, 2020 Severity: 3-Major
When using the rewrite profile, unchunked server responses where content-type is not text/HTML or text/CSS also gets converted to chunked encoding in client-side. Also, the server response is missing a message-body (no content-type/content-length). The client device receives 'Transfer-Encoding: chunked' in the message-header and receives a chunked body if the origin response has a message-body. The client receives a zero-length chunk if the origin response has no message-body. Prior to BIG-IP version 15, chunking happens only if origin server response has content-type header set to either text/HTML or text/CSS.
End users may notice a change in chunking behavior after upgrading from prior release.
- HTTP profile response chunking is set to 'sustain'. - The virtual server has rewrite profile attached. - Server response has content-type not set to text/HTML or text/CSS or no content-type header.
Use response chunking mode 'unchunk'.