How works the Headers encoding between Policy Server,
Web Agent and browser ?
The Policy Server sends the responses to
Web Agent in UTF-8 encoding only. It does
not apply any conversion at this level.
The conversion is applied by Web Agent before
sending these responses to the browser using
the “httpheaderencodingspec” parameter as
specified in the Web Agent configuration
(Agent Config object), to encode these responses
into further different encodings.
The HTTPHeaderEncodingSpec setting affects
the encoding of all HTTP Header values and
all custom HTTP-COOKIE Responses.
The syntax for the parameter is:
encoding_spec is a text string that represents
one of the following encoding types:
UTF-8, Shift-JIS, EUC-J, or ISO-2022-JP.
wrapping_spec is the wrapping specification,
which must be RFC-2047.
Although this variable is optional, it is strongly
recommend that wrapping specification is included
because the encoding type chosen may generate byte
codes that are not compatible with the HTTP protocol.
This is especially true while using custom HTTP Cookie
responses that contain double-byte encoded data.
For example, some Shift-JIS characters cause undesirable
results if they are not further encoded by RFC-2047.
The wrapping also tells the receiving application the
type and nature of the encoding so the application can
better interpret the encoded text. For example, you
may set the parameter to Shift-JIS,RFC-2047.
When RFC-2047 is used, the Agent first encodes the data
based on the chosen encoding specification and then
further encodes the data following the RFC-2047
If the HTTPHeaderEncodingSpec setting is left as blank,
the default is UTF-8 with no wrapping.