...
| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Use this policy with for highly reoccurring and static responses to manage latency and response times, and which reduce the load on the upstream API as well as the proxy server. An incoming HTTP request to one of your Proxy endpoints returns the cached response after that’s stored for a specified time period.
The API policy owner can control time intervals and configure query strings or headers so that you can cache responses that contain those configure the cache time-to-live (TTL) per policy, and the cache key used to cache each request (with every key-value pair).
In the policy settings, you specify the cache key parameters that the HTTP requests map to and set the cache response time and refresh interval.
| Info |
|---|
The default configuration is that the caches 85.83 MB of the payload. To customize the amount of cache stored in memory, consult your CSM. |
Because API Versions use endpoints generated in the SnapLogic IIP, the HTTP Response Cache policy supports Proxy endpoints only by design. In the UI, the API Policy Manager menus API and Version Details tabs do not display this policy.
Policy Execution Order
This policy is applied after all other API policies. All the security, authorization and traffic-shaping policies occur before this policy is appliedruns after every request and response policy.
Known Issue
Both the HTTP Cache Response and HTTP Retry Policies fail to evaluate expressions. As a result, the When this policy should be applied field should not be set. Doing so can cause issues with the way the policy is applied.
...