APAR status |
Closed as documentation error.
| Error description
Documentation on how and where to set character encoding within
WebSphere is limited. This defect will address recent changes
in this are at WAS 3.5.6 and clarify what it is at previous
levels. Local fixProblem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application *
* Server Version 3.5. *
****************************************************************
* PROBLEM DESCRIPTION: How to determine the request and *
* response encoding. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The following search order determines the request encoding
used by the Web container when handling the request (post or
query string) data:
1. If the default.client.encoding property is set, use the
client encoding.
2. Use the charset from the Content-type header, if it is
present.
3. If the charset information is not present, try to determine
the locale from the request using the Accept-Language HTTP
header. If the Accept-Language HTTP header does not contain
any language information, or if it contains an asterisk (*),
or if it is not present, skip to step 5.
4. If the charset information is not present, try to determine
the charset from the request using the Accept-Charset HTTP
header.
5. If the default.client.encoding property is not present,
use ISO-8859-1.
The following search order determines the response encoding
used by the Web container when creating a writer for the
response data:query string) data:1. If the default.client.encoding property is set, use theclient encoding.2. Use the charset from the Content-type header, if it ispresent.3. If the charset information is not present, try to determinethe locale from the request using the Accept-Language HTTPheader. If the Accept-Language HTTP header does not containany language information, or if it contains an asterisk (*),or if it is not present, skip to step 5.4. If the charset information is not present, try to determinethe charset from the request using the Accept-Charset HTTPheader.5. If the default.client.encoding property is not present,use ISO-8859-1.The following search order determines the response encodingused by the Web container when creating a writer for the
1. Use the charset from the response Content-type header,
if it is present.
2. If the default.client.encoding property is set, use that
encoding.
3. Use the charset from the Content-type header, if it is
present.
4. If the charset information is not present, try to determine
the locale from the request using the Accept-Language HTTP
header. If the Accept-Language HTTP header does not contain
any language information, or if it contains an asterisk (*),
or if it is not present, skip to step 6.
5. If the charset information is not present, try to determine
the charset from the request using the Accept-Charset HTTP
header.
6. If the default.client.encoding property is not present,
use ISO-8859-1.
Note: If the converter.properties file exists, check if
override exists for that character encoding. If override
exists, use that value for creating the PrintWriter. response data:1. Use the charset from the response Content-type header,if it is present.2. If the default.client.encoding property is set, use thatencoding.3. Use the charset from the Content-type header, if it ispresent.4. If the charset information is not present, try to determinethe locale from the request using the Accept-Language HTTPheader. If the Accept-Language HTTP header does not containany language information, or if it contains an asterisk (*),or if it is not present, skip to step 6.5. If the charset information is not present, try to determinethe charset from the request using the Accept-Charset HTTPheader.6. If the default.client.encoding property is not present,use ISO-8859-1.Note: If the converter.properties file exists, check ifoverride exists for that character encoding. If overrideexists, use that value for creating the PrintWriter. Problem conclusion
Close this APAR as a documentation change
(V3.5.7 Release Notes) Temporary fixComments
APAR information | APAR number | PQ67622 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED DOC | PE | NoPE | HIPER | NoHIPER | Submitted date | 2002-10-25 | Closed date | 2002-12-03 | Last modified date | 2002-12-03 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
Applicable component levels |
|