Bug ID 1294381: Variable assign handles some error cases disgracefully

Last Modified: Dec 18, 2024

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

Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1

Opened: May 02, 2023

Severity: 3-Major

Symptoms

1. Unable to add a Variable assign entry after correction which was first tried to add with incorrect syntax. 2. Existing variable assign entries are getting affected by showing in base64 encoding format even after deletion of incorrect entry added in point 1.

Impact

Existing variable assign entries are affected by changing to base64 format and we need to again add all the entries from the beginning which is incorrect.

Conditions

1. There should be existing Variable assign entries. 2. Newly added entry should contain space at the beginning or end of the session variable name.

Workaround

None

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips