Bug ID 876581: JavaScript engine file is empty if the original HTML page cached for too long

Last Modified: Jul 12, 2023

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

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 16.0.0,

Fixed In:
16.1.0, 16.0.1, 15.1.1,,

Opened: Feb 04, 2020

Severity: 3-Major


JavaScript engine file is empty.


No FPS protection for that HTML page.


Original HTML page with FPS injected content is cached for too long due to some caching headers (e.g., ETag), so the JavaScript engine link becomes invalid.


You can use either workaround: -- Use an iRule to disable caching for protected HTML pages. -- Set caching time for protected HTML pages to the same value as the datasync tables regeneration timer according to the active datasync profile (default value is two 2 days).

Fix Information

FPS now also removes ETag headers from protected HTML pages.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips