Bug ID 595946: Expired Timestamp violation is triggered too often

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6

Fixed In:
13.0.0

Opened: May 26, 2016
Severity: 3-Major

Symptoms

Expired Timestamp violation is frequently encountered by benign traffic. This occurs whenever there is an interval of at least 10 minutes between requests by a particular browser.

Impact

The Expired Timestamp violation is triggered and traffic may be blocked.

Conditions

The Expired Timestamp violation is enabled, and there is an interval of at least 10 minutes between requests by a particular browser.

Workaround

Disable Expired Timestamp violation.

Fix Information

All predefined policy templates have Expired Timestamp disabled.

Behavior Change