Bug ID 515226: Inconsistent internal handling of special characters used in 'name' fields

Last Modified: Sep 13, 2023

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

Known Affected Versions:
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.4, 11.6.5,,,, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:

Opened: Mar 30, 2015

Severity: 3-Major

Related Article: K31404493


For certain fields, there is inconsistent handling of the escaping process between the iControl REST API and the TMSH command line. When querying or displaying an 'object', the name must be provided to the query in the same way as it is returned, to ensure that different operations that access an object can always refer to the object the same way.


For some cases where characters )for example, a double or single quote) is used in an object name, the overall 'set' operation might fail during the 'verify' step. Further, the resulting object name might contain extra characters, making it impossible to execute an explicit 'verify' operation without using the TMUI.


Setting an object has two steps: the 'set', and the 'verify'. In the case of a special character contained in the object name, the 'set' operation might work, but the 'verify' might not. In some cases, the 'set' operation might include some internal 'escape' characters in the final object name.


Avoid using special characters for object names. This includes, for some applications, characters from the non-basic English character set; that is include only the following characters: A-Z, a-z, 0-9, and _ (underscore).

Fix Information

Handling of special characters used in 'name' fields has been updated to common handling procedures.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips