Using a special character in a URI
Information Console URIs use encoding for characters that a browser can misinterpret. The following example uses hexadecimal encoding in the Information Console URI to display the report, Newsfeed.rptdesign, from a volume:
You do not have to use hexadecimal encoding in all circumstances. Use the encoding only when the possibility of misinterpreting a character exists. The following unencoded URI displays the same report as the preceding URI:
Always encode characters that have a specific meaning in a URI when you use them in other ways. Table 19‑1 describes the available character substitutions. An ampersand introduces a parameter in a URI, so you must encode an ampersand that appears in a value string. For example, use:
instead of:
Table 19‑1 Encoding sequences for use in URIs
Encoded substitution
ampersand (&)
asterisk (*)
at (@)
backslash (\)
colon (:)
comma (,)
dollar sign ($)
double quote (")
equal (=)
exclamation (!)
forward slash (/)
greater than (>)
less than (<)
number sign (#)
percent (%)
period (.)
plus (+)
question mark (?)
semicolon (;)
space ( )
underscore (_)
If you customize Information Console by writing code that creates URI parameters, encode the entire parameter value string with the encode(  ) method. The encode(  ) method is included in encoder.js, which is provided in the Information Console <context root>/js directory. The following example encodes the folder name /Training/Sub Folder before executing the getFolderItems action:
<%-- Import the StaticFuncs class. --%>
<%@ page import="com.actuate.reportcast.utils.*" %>
String url =
"" +
StaticFuncs.encode("/Training/Sub Folder");
The encode(  ) method converts the folder parameter value from:
/Training/Sub Folder
UTF-8 encoding
All communication between Information Console and iHub uses UTF-8 encoding. UTF-8 encoding is the default encoding that web browsers support. For 8-bit (single-byte) characters, UTF-8 content appears the same as ANSI content. However, if extended characters are used (typically for languages that require large character sets), UTF-8 encodes these characters with two or more bytes.
All Information Console web pages support UTF-8 encoding. When customizing these pages or adding customized web pages to a Information Console web application, provide UTF-8 encoding support using the following code:
<META HTTP-EQUIV="Content-Type"
CONTENT="text/html; charset=utf-8">