PI58218: IBM HTTP Server mod_cache fixes

8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• While validating the freshness of a cached entity, IHS may
  return a 304 response to an unconditional request if the
  backend returns a 304 response without an "Expires" or
  Cache-Control header.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM HTTP Server users of the                *
  *                  mod_cache modules                           *
  ****************************************************************
  * PROBLEM DESCRIPTION: Unexpected 304 response can be sent     *
  *                      when using mod_cache                    *
  ****************************************************************
  * RECOMMENDATION:  Apply this fix if you use the mod_cache     *
  *                  modules of IHS                              *
  ****************************************************************
  IHS may return a 304 response when mod_cache is being used if
  the backend returns a 304 response for a freshness check.
  

Problem conclusion

• A 304 response will now be prevented for an unconditional
  request when the backend responds to a freshness check with a
  304 but no new expiration info.
  
  This fix is targeted for IBM HTTP Server fix packs:
  - 7.0.0.43
  - 8.0.0.13
  - 8.5.5.10
  

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

  IBM HTTP SERVER

• Fixed component ID

  5724J0801

Applicable component levels

• R700 PSY

     UP

• R800 PSY

     UP

• R850 PSY

     UP