On this page

Overview

Use this policy for highly reoccurring and static responses to manage latency and response times, 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 that’s stored for a specified time period.

The policy owner can 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.

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 runs 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.

Architecture

Each Snaplex node has its own cache, so the cache for an incoming request might miss on each node until properly distributed and hydrated on each node.

By default, the following cache keys are used:

Protocol
Host
Path
HTTP Method

The policy supports incorporating headers and query parameters as part of the cache key (not to access the cache key). The headers and query parameter values are used as part of the generated cache key to ensure unique cache entries as needed.

Usage Guidelines

We limit each policy to have 100 entries in the cache per policy. Accordingly, the policy evicts the least used entry after 100.
Expired caches cannot be accessed, and new entries overwrite any existing ones. The maximum quantity of bytes that an HTTP response caches in the default configuration is 85.83 MB of the payload.

These properties are configurable through Feature Flags. Refer to your CSM to modify these property settings.

Limitations

Each response cache can only contain 85 MB. The policy always returns the response, but any data over the limit renders the payload incomplete without notice.
A response cache is not effective to use for POST and PUT HTTP methods because these operations are meant to alter the state of data, and therefore should not be cached.

Settings

Parameter Name	Description	Default Value
Label	Required. The name for the API policy.	HTTP Respone Cache
When this policy should be applied	An expression-enabled field that determines the condition to be fulfilled for the API policy to execute. For example, if the value in this field is `request.method == "POST"`, the API policy is executed only if the request method is a POST.	N/A
Cache Interval	The time period of the current cache before it is evicted.	1
Time Unit	The time unit for the Cache Interval value.	Hour
Use HTTP Request Headers to Create Cache Keys	Enables use of all header values as part of the generated cache key.	Unselected
Use HTTP Request Query Parameter to Create Cache Keys	Enables use of all query parameter values as part of the generated cache key.	Unselected
Status	Specifies whether the API policy is enabled or disabled.	Enabled

Example

The policy supports using headers and query parameters to generate keys:

We recommend that the header and query string keys can be configured for caching HTTP responses with unique key-value pairs. For example, in a REST GET endpoint that multiplies two integers:

GET
/gateway/proxy/multiply?intA=[valueA]&intB=[valueB]

Configuring the policy to use query strings intA and intB to cache policies for every key-value pair that has query strings with intA and intB.

For example, the following GET requests each have a separate entry:

/gateway/proxy/multiply?intA=5&intB=5
/gateway/proxy/multiply?intA=2&intB=2
/gateway/proxy/multiply?intA=3&intB=1

The following HTTP responses are cached so that the proxied server does not need to perform the calculation:

Response 1 
{
    "operation": "5 x 5", 
    "result": 25
}

Response 2 
{
    "operation": "2 x 2", 
    "result": 4
}

Response 3
{
    "operation": "3 x 1", 
    "result": 3
}

If int C x int D were existing parameters, they would not be cache, because they're not configured in the policy.

The entire HTTP response is cached, including headers.

Best Practice

Do not use any headers and query string parameters like a timestamp as part of your cache key or it never results in a cache hit.

You can optionally strip those headers using the Request Transformer policy. Alternatively, avoid headers/query string parameters as part of the cache key as needed when a unique value is present per request.

HTTP Response Cache UAT