1-34
Cisco ASA Series CLI Configuration Guide
Chapter 1 Configuring Clientless SSL VPN
Encoding
Detailed Steps
Step 1 Global Encoding Type determines the character encoding that all clientless SSL VPN portal pages
inherit except for those from the CIFS servers listed in the table. You can type the string or choose one
of the options from the drop-down list, which contains the most common values, as follows:
• big5
• gb2312
• ibm-850
• iso-8859-1
• shift_jis
Note If you are using Japanese Shift_jis Character encoding, click Do not specify in the Font Family
area of the associated Select Page Font pane to remove the font family.
• unicode
• windows-1252
• none
Note If you click none or specify a value that the browser on the clientless SSL VPN session does not
support, it uses its own default encoding.
You can type a string consisting of up to 40 characters, and equal to one of the valid character sets
identified in http://www.iana.org/assignments/character-sets. You can use either the name or the alias of
a character set listed on that page. The string is case-insensitive. The command interpreter converts
upper-case to lower-case when you save the ASA configuration.
Step 2 Enter the name or IP address of a CIFS server for which the encoding requirement differs from the
“Global Encoding Type” attribute setting. The ASA retains the case you specify, although it ignores the
case when matching the name to a server.
Step 3 Choose the character encoding that the CIFS server should provide for clientless SSL VPN portal pages.
You can type the string, or choose one from the drop-down list, which contains only the most common
values, as follows:
• big5
• gb2312
• ibm-850
• iso-8859-1
• shift_jis
Note If you are using Japanese Shift_jis Character encoding, click Do not specify in the Font Family
area of the associated Select Page Font pane to remove the font family.
• unicode
• windows-1252
• none
To Next Page
Loading...
Need help?
General
