IBM Support

PK27527: DEFAULT CONTENT-TYPE SETTING ON VERSION 6 IS "TEXT/PLAN" DAFAULT VALUE IN VERSION 5 IS "TEXT/HTML"

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In WebSphere 5.1.x the default content-type setting is
    "text/html" where as 6.0.x has default content-type setting is
    "text/plan". This change is as per specification but does not
    support backword compatibility
    

Local fix

  • a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: WebSphere Application Server users of        *
    *                 version 6.                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: The default Content-Type sent by        *
    *                      WebSphere Application Server has        *
    *                      changed from versions 4 to 5 to 6 due   *
    *                      to specification changes.               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In version 6, we are currently adhering to the servlet 2.4
    specification in which no default content type is set. But
    when a getWriter call is made, we append the current response
    character encoding if the Content-Type header has no charset
    element yet. This is a change from version 4 and version 5.
    Also, in version 4 the default content-type was text/html,
    while in version 5 it was text/html;charset =
    default_encoding_of_system where default_encoding_of_system is
    typically ISO-8859-1.
    
    We will provide a way for customers to have Content-Type
    behavior function like version 4 or 5.
    

Problem conclusion

  • The webcontainer custom property
     com.ibm.ws.webcontainer.contenttypecompatibility was
    introduced to allow the customer to specify either "V4" or
    "V5" as the value of which version behavior they wish to use.
    
    The fix for this APAR is currently targeted for inclusion
    in fixpacks 6.0.2.13 and 6.1.0.2.
    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

    PK27527

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    60I

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-07-05

  • Closed date

    2006-07-31

  • Last modified date

    2006-08-22

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

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

Modules/Macros

  • ENGINE
    

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
19 October 2021