Last Modified: Apr 17, 2024
Affected Product(s):
BIG-IP Install/Upgrade, LTM
Known Affected Versions:
15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4
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'.
None