Bug ID 694288: VPE object names cannot contain special characters

Last Modified: Dec 20, 2018

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4

Fixed In:
14.0.0

Opened: Nov 13, 2017
Severity: 4-Minor

Symptoms

When a VPE object is created or renamed with one or more special characters, the characters are silently removed and the name of the object is saved without them. Special characters stripped from name of the VPE object when creating or renaming said VPE object

Impact

There is no functional impact. This is working as expected even though it is not documented.

Conditions

VPE object is created or renamed with one or more of the following special characters: `~!@#$%^&*={}|:"<>?\;',.?

Workaround

Do not include special characters when naming a VPE object.

Fix Information

The system now posts the following message in this case: VPE objects, such as a message box or macro, cannot contain special characters such as brackets, exclamation points, or question marks. The VPE removes the special characters when saving the object. This is now documented. The following characters are not allowed in VPE object names: `~!@#$%^&*={}|:"<>?\;',.?

Behavior Change