This documentation is for WSO2 API Manager 1.8.0 View documentation for the latest release.
Page Comparison - Configuring Caching (v.8 vs v.9) - API Manager 1.8.0 - WSO2 Documentation

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

An API's resources are HTTP methods that handle particular types of requests such as GET, POST etc. They are similar to methods or function calls.There are parameters specific to an API's resource of a particular class. Each resource has parameters such as its throttling level, Auth type etc.

...

When a user makes a request to an API through any of its defined resources, the resource-level parameters are cached in the resource cache, at the Gateway node. For example, if you make a GET request to the API, the its Auth type (and other parameters) are cached at the Gateway. This and throttling level is cached. This cache entry is identified by a cache key, which is based on the API's context, version, request path and HTTP method.

Caching avoids the need to do a separate back-end call to check the Auth type and throttling level of the a resource, every time a GET request to the API happens. Resource caching It improves performance.

Note that if you change a resource's parameters such as the Auth type through the UI, it takes about 15 minutes to refresh the resource cache. During that time, the server returns the old Auth type from the cache. If you want the changes to be reflected immediately, please restart the server after changing the value.

...