Bug ID 468710: Using non-standard lettercasing for header name results in misleading error during commit of transaction

Last Modified: Oct 01, 2018

Bug Tracker

Affected Product:  See more info
BIG-IP All(all modules)

Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6

Fixed In:
11.6.0, 11.5.7

Opened: Jun 24, 2014
Severity: 3-Major
Related AskF5 Article:
K32093584

Symptoms

As part of adding commands to a transaction for iControl REST call, the header name to be used is "X-F5-REST-Coordination-Id." However, if you mix the letter casing to something else, such as: "x-f5-rest-coordination-id" then when you commit this transaction you will get this misleading error: "there is no command to commit in the transaction." Your command and transaction will succeed, but the error implies it did not.

Impact

It looks like the transaction failed, when in fact, it may have succeeded.

Conditions

Using the non-standard letter casing for that header name during the iControl REST call to add commands to a transaction.

Workaround

Use the proper letter casing for that header name as shown above.

Fix Information

Use the proper letter casing for that header name as shown above.

Behavior Change