PI46214: EDGE CACHING PROXY HAS A ISSUE WITH CACHEIGNORECOOKIENAME DIRECTIVE WITH MULTIPLE ENTRIES.

8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
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
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
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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

• Edge Caching Proxy has a issue with CacheIgnoreCookieName
  directive with multiple entries.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  ALL                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: Edge Caching Proxy has a issue with     *
  *                      CacheIgnoreCookieName                   *
  *                      directive with multiple entries..       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  CacheIgnoreCookieName  ¢â‚¬â€œ Cache the response with Set-Cooki
  header having the cookie name.
  Normally Caching Proxy will junk the responses if there is
  Set-Cookie header in the response from the backend server.
  Use this directive to cache the response with Set-Cookie
  header if the cookie name in the header  matches the name
  given in this directive.
  The CacheIgnoreCookieName only handles one cookie and does not
  allow wild card characters. You need to have a new
  CacheIgnoreCookieName directive for every cookie name for
  which the response has to be cached.
  Format
  CacheIgnoreCookieName cookie_name
  Example
  CacheIgnoreCookieName abcde
  CacheIgnoreCookieName xyz_123
  Default
  None
  Because of the presence of the Set-Cookie header in the
  response from the backend server, CP is junking the responses.
  CacheIgnoreCookieName directive will make sure that the
  response won't be junked. If there are multiple entries of the
  CacheIgnoreCookieName dirctive, CP was not working as expected.
  

Problem conclusion

• Made appropriate code changes to correct this issue.
  The fix for this APAR is currently targeted for inclusion in
  fix packs 8.5.5.8, 8.0.0.12 and 7.0.0.16
  

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 CACH PROXY

• Fixed component ID

  5724H8810

Applicable component levels

• R700 PSY

     UP

• R800 PSY

     UP

• R850 PSY

     UP