PK76114: DYNAMICCACHE IS NOT PROPERLY CACHING THE CHARSET IN CONTENT-TYPE HEADER

Fixes are available

APAR status

Closed as program error.

Error description

Cached servlet content does not preserve the original
Content-Type header. The problem is seen with a servlet that
does the following:
 response.setContentType("application/x-javascript");
 response.setCharacterEncoding("UTF-8");
 ... includes content from several javascript files ...

With servlet caching disabled, this is working fine. The
response includes the following header:
 Content-Type: application/x-javascript; charset=UTF-8

With servlet caching enabled, cached responses are missing the
";charset=UTF-8" portion of the Content-Type header, resulting
in:
  Content-Type: application/x-javascript

This causes UTF-8 characters in the response data to be
corrupted.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server Version    *
*                  6.0.2, 6.1 and 7.0 users with?servlet       *
*                  caching?enabled.                            *
****************************************************************
* PROBLEM DESCRIPTION: You will get a garbled output if the    *
*                      cached response is dependent on         *
*                      setContent and/or                       *
*                      setCharacterEncoding on setting the     *
*                      charset value of the Content-Type       *
*                      header                                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Cached servlet content does not preserve the original
Content-Type header and as a result Cached responses will be
missing the ;charset=xxx portion of Content-Type header. In
the reported customer problem with servlet caching enabled the
response header was missing ;charset=UTF-8 portion of
Content-Type header.

Problem conclusion

Code has been updated so that the original Content-Type
header is preserved in the cached servlet content and used
to create the Content-Type header for cached responses.
However, the following WebContainer custom property needs to
be set to enable this new behavior for versions 6.0.2 and 6.1:

com.ibm.ws.webcontainer.contenttypecompatibility = "V7".

Please refer to the following technote for instructions on
enabling WebContainer custom properties:
http://www.ibm.com/support/docview.wss?rss=180&uid=swg21284395

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.5, 6.1.0.25 and 6.0.2.35.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK76114
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-11-20
Closed date
2009-03-24
Last modified date
2009-03-24

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK76114: DYNAMICCACHE IS NOT PROPERLY CACHING THE CHARSET IN CONTENT-TYPE HEADER

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?