Auto - Netscape ENTREPRISE SERVER 6.1 - 08-2002 ADMINISTRATOR Administrator's Manual

• url-encodes the
POST
• Sets the Content-Type to
• Does not send any charset information in the
On the server side, if a servlet tries to access
getParameterValues
which character encoding to use for
You can configure Enterprise Server 6.1 to instruct the servlet container which
character encoding to use for interpreting
specify the character encodingusing the
:
web-apps.xml
<parameter-encoding enc="value"/>
where value can be one of the following:
• (default)

auto

• none
• any valid encoding
These values are described below.
auto
requires the servlet container to look for some hints regarding the character
auto
encoding to be used. The hint can be provided using:
• A request attribute with the name:
com.netscape.server.http.servlet.parameterEncoding
type . The request attribute must be set before any calls to
String
getParameter()
request.setAttribute("com.netscape.server.http.servlet.
parameterEncoding", "Shift_JIS");
request.getParameter("test");
This option is used if the servlet knows beforehand what the charset of the
posted data is.
• A parameter in the form data. The form that is being submitted
j_encoding
can have a hidden element. Example:
<input type=hidden name="j_encoding" value="Shift_JIS" >
data
application/x-www-form-urlencoded
, the servlet container does not have any information about
getParameter
POST
parameter-encoding
or
getParameterValues()
Servlet Internationalization
header
Content-Type
data using
POST getParameter
strings.
data strings. To do this, you would
element in
. The value is of
. Example:
Appendix D International Content Support
or
359