PM27224: THE HTTP CHANNEL CAN RETURN AN INCORRECT CHARSET WHEN PARSING IT FROM THE CONTENT-TYPE HEADER

6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• The call to getHeaderAsString to parse out the Content-Type
  fails in the underlying parse code for the headers. An FFDC will
  be generated with this at the top of the stack trace:
  
  Stack Dump =
  java.nio.charset.IllegalCharsetNameException: utf-8"
  at java.nio.charset.Charset.checkName(Charset.java:326)
  at java.nio.charset.Charset.lookup(Charset.java:499)
  at java.nio.charset.Charset.forName(Charset.java:537)
  

Local fix

• test fix
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server Version    *
  *                  6.1 and 7.0 users                           *
  ****************************************************************
  * PROBLEM DESCRIPTION: The HTTP Channel can return an          *
  *                      incorrect charset when parsing it       *
  *                      from the content-type header            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When parsing the charset from the content-type, the HTTP
  Channel could return an incorrect charset if it is located
  first within another attribute(such as start-info) For
  example, this string would not parse correctly:
  Content-Type: multipart/related;
  type="application/xop+xml";start-info="text/xml;
  charset=utf-8";
  start="<1842026614189.1232731018211.IBM.WEBSERVICES@swappu40>";
  charset=utf-8;
  The result of parsing the above content-type for the charset
  would be the value: utf-8". When we parsed the above string we
  would search for the first occurrence of "utf-8". This would
  end up with an FFDC logged for an invalid charset.
  

Problem conclusion

• The HTTP channel was modified to be more robust when parsing
  the charset from the content-type. Now it will look for each
  charset in the string and determine if it's within a set of
  quotes or not. The charset outside of any quotes will be
  returned, if it's not found it will return the default charset.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 6.1.0.37 and 7.0.0.17.  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 is sysrouted FROM one or more of the following:

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

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP

• R700 PSY

     UP