Bug ID 669306: The HTTP_DISABLE iRule event may cause a TMM crash

Last Modified: Sep 13, 2023

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

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0

Opened: Jun 14, 2017

Severity: 2-Critical

Related Article: K12127978

Symptoms

The HTTP_DISABLE iRule event is invoked when the HTTP filter is enabled or disabled. If this occurs before the first HTTP request is released, then the TMM may crash.

Impact

A TMM core. Traffic disrupted while tmm restarts.

Conditions

-- The HTTP_DISABLE iRule event is used. -- HTTP is disabled before the first request reaches the HTTP filter. (This might occur if TCP::collect is used, or if HTTP::disable is invoked in CLIENT_ACCEPTED.)

Workaround

None.

Fix Information

The HTTP_DISABLE event now works in the described case without causing a TMM crash.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips