Tealeaf supports internationalization (the use of native non-English character sets) in monitored applications.
Tealeaf supports ISO-8859-1 and UTF-8 encoding only. If needed, you can configure the PCA and the Windows pipeline to handle traffic that is in ISO-8859-1 and UTF-8 encoding.
Tealeaf provides limited support for double byte encoding.
International character set support
Tealeaf provides limited support for UTF-8 and ISO-8859-1 character sets.
- Monitored web sites must use either ISO-8859-1 or UTF-8 character encoding and may not mix them.
- Some searching and filtering operations (such as privacy and filtering rules) may not correctly process non-ASCII data (characters outside of A-Z, a-z, 0-9, and common punctuation).
- Some user interface components do not respect cultural preferences for dates, times, calendars, and numbers.
- Some components of Tealeaf CX (including PCA, HBR, and RTV) do not properly process user data that cannot be represented in the native character encoding of the operating system.
For example, these components would not process Arabic data correctly on a French Windows system. Customers should match the native character encoding of their operating system with the encoding of the data being processed.
The following table provides information about international character set support available in Tealeaf component features.
| Tealeaf function | Support notes |
|---|---|
| Passive Capture Application |
|
| Windows pipeline | In the Windows pipeline, the Inflate session agent automatically scans for buffer variables that are inserted by the Passive Capture Application to support internationalization. If these variables are not present, the Inflate session agent adds them. This feature requires no additional configuration. |
| Indexing | Indexes are generated in UTF-8 encoding. |
| Canister Storage | Response bodies are converted to UTF-8 for indexing. You can search for text in the response.
Since the request data has already been converted to UTF-8 encoding, it can be searched through standard search mechanisms. All Tealeaf-internal data associated with a session is stored in UTF-8 encoding. |
| Portal | The Portal can be localized in UTF-8 to any supported character set.
The Portal inherits its number formatting from the operating system settings of the machine hosting the Portal application. |
| Search | Through the Portal, you can search for international characters in both the request and the response. |
| Event Manager | In the definition for a hit attribute, you can select the encoding to expect in the request data. This value should match the value configured for the PCA. |
| Browser Based Replay | Browser Based Replay support the UTF-8 character set. |
| RTV Replay | RTV is not a UNICODE application and therefore does not support search for multi-byte characters.
RTV can replay the Response page in whatever code format is specified in the Response HTTP Content-type/encoding directive. The request buffer continues to be replayed in English UTF-8 format. |
| cxConnect for Data Analysis | cxConnect for Data Analysis can be configured to extract extended characters in UTF-8 format. |
Internationalization request variables
REQ_BUFFER_ENCODING=UTF-8
REQ_BUFFER_ORIG_ENCODING=ISO-8859-1
RESP_BODY_ENCODING=utf-8Affected Systems
The following Tealeaf systems use the variables described in the previous section to identify international encoding schemes and to interpret captured data accordingly.
- RTV
- Event Manager
- CX Browser Based Replay
- Extended Privacy Session Agent
- Event evaluation