JR52613: REST responses with error status codes are being cached

APAR status

• Closed as program error.

Error description

• REST API requests which return with error status codes are being
  cached. This is causing future good requests to return with the
   results of the prior cached error response.
  

Local fix

• Clearing the dynacache is the current workaround to avoid stale
  data being kept in dynacache.
  

Problem summary

• USERS AFFECTED:
  The shoppers who browse on a store.
  
  PROBLEM ABSTRACT:
  REST responses with error status codes are being cached
  
  BUSINESS IMPACT:
  User and application errors might be returned as cached
  responses.
  
  RECOMMENDATION:
  

Problem conclusion

• A default Accept string "*/*;q=0.1" will be added to any REST
  Tag request that doesn't have "*/*" wildcard. It will avoid
  exception generated due to browsers not having the supported
  media type. It is to facilitate the REST Tag to retrieve useful
  JSON information no matter what Accept header the browser has.
  
  In addition, the server code has been updated to set response
  un-cacheable when there is an exception encountered by the
  server.
  
  The sample cachespec.xml file has been updated for
  Search-Rest.war so that "format" (instead of "responseFormat")
  will be used as a cache rule attribute. It is set a clear
  separation between callers with different Accept header when the
   REST request is called directly by broswer's javascript and
  responseFormat is not specified.
  

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

  WC BUS EDITION

• Fixed component ID

  5724I3800

Applicable component levels

• R700 PSY

     UP