Skip to main content
Skip table of contents

Caching Resources

With the Caching Resources policy it is possible to cache requests based on their URL path, HTTP method and HTTP status code. This allows reducing overall traffic to the backend API.
The size of the cache to be used can be defined in the Advanced API Management Settings.

If you want to cache POST requests, you have to enable stateful request payload inspection in your API Implementation.

Configuration Options

All rules that have been defined are listed in section Cached Resources.

Global Caching Settings

OptionDescriptionAllowed Values
Cache API responses forSpecify a duration in seconds for how long the resources are cached (time-to-live).any long integer

Caching Resources Rule

OptionDescriptionAllowed Values
Path Pattern
Enter a regular expression that will be used to identify the REST resource to cache. This applies to the resource path from the API endpoint on, e.g. http://bridge.scheer-acme.com:19038/support /supportcases.a valid regular expression
HTTP Method

Specify a HTTP method to apply the path pattern to.

If you want to cache POST requests, you have to enable stateful request payload inspection in your API Implementation.

You will get a hint as soon as you add a rule containing *  or POST:

*Cache all allowed methods (see below).
GET

Cache GET requests only.

POSTCache POST requests only.
HEADCache HEAD requests only.
Status Code

Specify a status code that will be used to identify the REST resource to cache.

*Cache all status codes.
a specify status codeCache this specific status code only.

Related Documentation:

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.