PM55554: CACHING PROXY DOES NOT PARSE THE ENTIRE HEADER NAME IN DETERMINING THE HEADER FIELD NAME.

APAR status

• Closed as program error.

Error description

• Caching Proxy does not parse the entire header name in
  determining the header field name.  This can cause problems if
  the client creates a user header such as "host-software:" and
  the code just checks the first 4 characters for host and assumes
  it is the host header.
  

Local fix

Problem summary

• Caching proxy does a regular string like match when parsing the
  header field after it identifies a standard pattern in the
  header. For eg. HOST*. This behaviour affects those users who
  want to have custom headers. For eg. HOST_SOMETHING will be
  treated as HOST itself.
  

Problem conclusion

• The fix performs an exact match for the header. It is fixed in
  6.1.0.28, 7.0.0.8, 8.0.0.3 and later versions of proxy.
  

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

• R610 PSY

     UP

• R700 PSY

     UP

• R800 PSY

     UP