Cisco Enterprise CDN Software

Files with Special Characters in ECDN

Document ID: 4177

Updated: Jan 31, 2006



Enterprise CDN (ECDN) Version 3.0 ensures that all filenames will be supported by all systems that interact with it by eliminating certain characters. These restricted characters are either removed from the filename or converted in the filename at the time the file is imported. This document lists those characters, how they are handled, and what problems this may present to a system administrator.

Before You Begin


For more information on document conventions, see the Cisco Technical Tips Conventions.


There are no specific prerequisites for this document.

Components Used

The information in this document is based on the software and hardware versions below.

  • ECDN v3.0.1 and v3.0.2

The information presented in this document was created from devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If you are working in a live network, ensure that you understand the potential impact of any command before using it.


Restricted Characters

Different systems and different applications may have different restrictions on what characters can be used in a filename. To ensure that all filenames on the ECDN can be supported by other systems, restricted characters are either converted or eliminated entirely at the time the file is imported. The table below lists the restricted characters that are removed from the filename if present.

Character Name
" double-quote
/ forward-slash
' single-quote
\ backslash
: colon
* asterisk
? question mark
< less than
> greater than
~ tilde
| vertical bar
! exclamation point
@ at
# pound
$ dollar
% percent
^ caret
& ampersand
( open parenthesis
) closed parenthesis
` backquote
+ plus sign
= equals sign
{ open brace
} closed brace
[ open bracket
] closed bracket
; semicolon
, comma


Besides these restricted characters, the space character is also a restricted character. Instead of removing the space, it is converted to an underscore.

Other Special Characters

Some non-alphanumeric characters are legal in filenames. These characters are neither removed nor converted.

Character Name
. period
_ underscore
- dash

Potential Conflicts

Because of the automatic conversion of filenames, it is possible to result in filenames that conflict. For example, the following filenames will all conflict as they will all result in the same filename ?Testing_this?:

Tes$ting this
Te~sting this
Testing ?this?

As a system administrator, you must ensure that filenames will not conflict once the file has been imported.

Related Information

Updated: Jan 31, 2006
Document ID: 4177