Bug ID 607246: Encrypted cookie insert persistence with fallback may not honor cookie after fallback expires

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.1, 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.1, 11.6.2, 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, 13.0.0

Fixed In:
13.1.0, 13.0.0 HF1, 12.1.3, 11.6.3

Opened: Jul 27, 2016

Severity: 3-Major

Symptoms

You notice erratic persistence behavior when you set cookie persistence to "required" in your cookie persistence profile

Impact

Persistence fails after fallback expired.

Conditions

Encrypted cookie persistence with fallback where the fallback persistence has a reasonable short timer such that a request containing a valid cookie is handled after the fallback entry has expired.

Workaround

Change cookie-encryption to preferred which allows persistence on either encrypted or decrypted cookie.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips