Loading...
Loading...
When either DoS Application Profile or Bot Defense profiles are used, or a complex LTM policy is used, the Accept-Encoding request header is removed by the BIG-IP system, which causes the backend server to respond with uncompressed payload. Second effect is that the Bot Defense Profile and L7 DoS profile are always, not conditionally, considered internally as a profile that modifies a body that satisfies HTTP profile chunking configuration 'sustain' (default mode) triggering client-side chunking. This causes a response in the server-side that is unchunked to be always chunked in client-side with the mode set to 'sustain'.
-- Response payload sent by the backend server is uncompressed. -- Performance impact caused by response parsing.
One of these options: -- Bot Defense Profile is associated with the Virtual Server. -- DoS Profile is associated with the Virtual Server and has Application (L7) enabled. -- Policy is associated with the Virtual Server and has complex LTM Policy: multiple Policies, or additional rules.
For version 15.1.0 and later, you can use the following workaround: Disable the option for modification of Referer header: tmsh modify sys db asm.inject_referrer_hook value false Note: Using this brings back the impact of ID792341 (see https://cdn.f5.com/product/bugtracker/ID792341.html). For versions earlier than 15.1.0, there is no workaround.
The system no longer removes the Accept-Encoding header and no longer parses response payload if not needed based on configuration.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.