Last Modified: Nov 07, 2022
See more info
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.10, 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, 11.5.7, 11.5.8, 11.5.9, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 11.6.4, 11.6.5, 188.8.131.52, 184.108.40.206, 220.127.116.11
Opened: Mar 30, 2015
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).
Handling of special characters used in 'name' fields has been updated to common handling procedures.