Bug ID 1600669: Inconsistency in iRule parsing for iControl REST and tmsh/WebUI

Last Modified: Sep 27, 2024

Affected Product(s):
BIG-IP LTM(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, 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, 17.0.0, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4

Opened: Jun 25, 2024

Severity: 4-Minor

Symptoms

After sending iRule content with POST via iControl REST - 400 error is returned similar to below: {"code":400,"message":"can't parse TCL script beginning with\n\nproc someproc {}{\n log local0. \"something\"\n}\n } \n","errorStack":[],"apiError":26214401}%

Impact

iRule is not added to BIG-IP and 400 error is returned

Conditions

iRule contains closing and opening curly brackets next to each other without a space e.g.: proc someproc {}{ instead of proc someproc {} {

Workaround

Add space between closing and opening curly brackets

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips