IBM Support

PH46638: SERVER MARKDOWN AND RETRY WHEN 505 IS RECEIVED INSTEAD OF 100-CONTINUE.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • server markdown and retry when 505 is received instead of
    100-continue.
    
    
    The 505 is a result of the customers RewriteRule's copying a
    decoded %3f / "?" and a decoded %20 / " " which results in an
    invalid request passed through to the WAS Plugin. If the path
    component of the URL contains escaped characters, this can
    happen when the decoded form is captured and re-substituted with
    RewriteRule.  The ? and " "  are not re-encoded automatically.
    
    
    I do not recommend making the rewrites more complicated to try
    to accommodate what are clearly pen test /  malicious URL's
    differently.  While it is easy to spot what is desirable to
    re-encode, we do not have fine-grained control over it in
    mod_rewrite.
    
    
    Plugin SC may still address the markdown resulting from the 505.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Plugin marks down a server from a 505   *
    *                      response code                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a 505 response code is received by the plugin from
    WebSphere, the plugin would mark that server down.  A 505
    response code is "Version not supported" which doesn't
    indicate that WebSphere itself is unresponsive.
    

Problem conclusion

  • The plugin has been fixed to recognize the 505 and return it
    back to the customer without marking down the server.
    
    The fix for this APAR is targeted for inclusion in fix pack
    8.5.5.23 & 9.0.5.13. For more information, see 'Recommended
    Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH46638

  • Reported component name

    IBM HTTP SERVER

  • Reported component ID

    5724J0801

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-05-20

  • Closed date

    2022-08-16

  • Last modified date

    2022-08-16

  • 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

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

Document Information

Modified date:
16 August 2022