PH35997: After upgrade to 9.0.5.7 static content which was previously being served by IHS was returning 404 error codes.

APAR status

• Closed as program error.

Error description

• After upgrade to 9.0.5.7 static content which was previously
  being served by Intelligent Management enabled web servers
  was returning 404 error codes.
  
  The ability to allow the IHS to server static content relies
  on the IHS not finding a match for the request in its
  routing data. 9.0.5.7 included APAR PH32919 which added the
  ability to carry url-patterns associated with filter-mapping
  definitions in the routing data Intelligent Management
  delivers to the web
  server. Post APAR PH32919, if web modules are present in the
  environment that do not define a context root and contain a
  filter-mapping pattern of '/*' that target becomes a catch
  all in the routing data Intelligent Management delivers to
  the web server and therefore no attempt to fall back to
  static routing
  by the web server is ever made resulting in 404s.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
  *                  WAS ND edition with Intelligent Management  *
  *                  enabled web servers configured to locally   *
  *                  serve static content.                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: Intelligent Management enabled web      *
  *                      servers configured to locally serve     *
  *                      static content fail to serve the        *
  *                      content returning 404 error codes.      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The ability for Intelligent Management enabled web servers
  (IMWS) to locally serve static content relies on the IMWS not
  finding a match for the request in its routing data so an
  attempt can be made to serve the content locally. APAR PH32919,
  included in fix packs 9.0.5.7 and 8.5.5.20, added carrying of
  url-patterns associated with filter-mapping definitions in the
  routing data used by IMWSs. If web modules are present in the
  environment that do not define a context root and contain a
  filter-mapping pattern of /*, that target becomes a catch all in
  the IMWS routing data and therefore no attempt will be made to
  serve the content locally as it would be matched in the routing
  data.
  

Problem conclusion

• This APAR, PH35997, adds a way to disable carrying the filter-
  mapping url-patterns in the Intelligent Management enabled web
  servers routing data via cell custom property
  odc.filterUrlSupport. Setting cell custom property
  odc.filterUrlSupport with a value of false, synchronizing the
  change, and restarting the dmgr will disable carrying the filter
  mapping url-patterns in the Intelligent Management enabled web
  servers routing data; reverting the behavior introduced in
  PH32919.
  
  The fix for this APAR is currently targeted for inclusion in fix
  packs 9.0.5.8 and 8.5.5.20.  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

• R900 PSY

     UP