Bug ID 464874: Client may legitimately send a range request for the cached JS/CSS content which is no longer valid.

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10

Fixed In:
11.6.0

Opened: May 29, 2014

Severity: 2-Critical

Symptoms

When JS/CSS minification feature is turned on, some client may legitimately send a range request for the cached JS/CSS content which is no longer valid due to content size reduction by the feature. In that case, TMM may spin out of control, and eventually be killed by SOD.

Impact

TMM becomes unresponsive and SOD will kill it.

Conditions

Client retrieves the JS/CSS content from WAM and get the unminified content. Turn on JS/CSS minification. Client issues range request for the JS/CSS content using the content size it knows about, which is prior to minification. WAM will try to serve to content with the range request, which technically is no longer valid due to content size shrinkage.

Workaround

Turn off JS/CSS minification

Fix Information

Fixed a situation where TMM may crash by SOD when JS/CSS minification is turned on and clients issue range requests.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips