Character considerations for rule upload

Special character support

You can use these characters for inbound/source URL matches:

{ } | \ ^ [ ] `

Invalid characters

Do not use the following characters in the CSV file you create for rule upload. They are invalid:

< > @ \ ¡ ¢ £ ¤ ¥ ¦ § ¨ © ª « ¬ ' ®
° ± ² ³ ´ µ · ¸ ¹ ¹ º » ¼ ½ ¾ ¿ À
Á Â Ã Ä Å Æ Ç È É Ê Ë Ì Í Î Ï Ð Ñ Ò Ó
Ô Õ Ö × Ø Ù Ú Û Ü Ý Þ ß à á â ã ä å æ
ç è é ê ë ì í î ï ð ñ ò ó ô õ ö ÷ ø ù
ú û ü ý þ ÿ

In addition, Unicode Private Use Area (PUA) characters are also invalid.

Characters with special uses

When setting up your CSV file for rule upload, the following characters have special uses:

Character Use
Encapsulates strings in field values.
# Denotes a comment when used at the start of a line, or when preceded by a space anywhere in a line. All other instances of this character is treated as a literal.

Valid Usage

Here is an example of a CSV file with valid comments:

ruleName,regex,result.redirectURL,result.statusCode

Rule3, http://example.com , http://example-new.com#redirect , 301

# For Rule3, the “#redirect” does not need to be escaped in CSV.

Invalid Usage

ruleName,regex,result.redirectURL,result.statusCode

Rule #1, http://example.com, http://example-new.com, 301

Rule2, http://example-shop.com, http://example-newshop.com, 301 \#

# Everything after “Rule “ in the above rule is treated as a comment.

# The “\#” in Rule2 is not a comment.