Bug ID 480509: Compression statistics for javascript content may be incorrectly classified

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
10.2.4, 11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4

Fixed In:
12.0.0, 11.5.2

Opened: Sep 22, 2014
Severity: 5-Cosmetic
Related AskF5 Article:
K16259

Symptoms

The compression statistic for 'Other' content increases unexpectedly when compressing javascript content

Impact

Misleading compression statistics

Conditions

This issue occurs when: - Virtual with compression profile - HTTP responses received with a Content-Type header value other than 'application/x-javascript'

Workaround

Use iRule to change Content-Type header: when HTTP_RESPONSE { if {[HTTP::header Content-Type] contains "text/javascript"} { HTTP::header replace Content-Type application/x-javascript log local0. "after [HTTP::header Content-Type]" } }

Fix Information

HTTP bodies containing a Content-Type header of 'application/javascript' or 'text/javascript' will be recorded under the 'Javascript' compression statistic.

Behavior Change