Bug ID 534500: TCL/Persist 'persist' command does not apply across connections.

Last Modified: Sep 13, 2023

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

Known Affected Versions:
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, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 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

Opened: Jul 21, 2015

Severity: 3-Major

Symptoms

When using iRules to configure persistence, if a client uses keepalive so that multiple requests come on the same connection, it is possible to write a conditional 'persist' command (e.g., to only persist based on certain requests).

Impact

Requests that are not processed in that conditional 'persist' revert to the persistence configuration of the virtual server.

Conditions

Using conditional 'persist' requests in an iRule.

Workaround

Ensure that all paths specifically declare persistence settings. To configure for no persistence for a given message, the iRule should have a call to 'persist none'.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips