MQSeries.net :: View topic - APIConnect || etags

aspre1b · Posted: Mon Jun 18, 2018 12:42 am Post subject: APIConnect || etags

Has anyone had any experience implementing etags and APIConnect caching in APIConnect?

An ETag is an opaque identifier assigned by a web server to a specific version of a resource found at a URL. If the resource representation at that URL ever changes, a new and different ETag is assigned. Used in this manner ETags are similar to fingerprints, and they can be quickly compared to determine whether two representations of a resource are the same.

We have a very simple API, which returns a static data set which changes every 3 months. There are no variables/parameters passed as part of the request, only standard headers.

The ETag is used to optimise browser calls, but we would like to enable API caching at the API Gateway (APIConnect), which would mean that APIConnect would need to be able to compare the ETag on the request header and compare it against the cached payload. If the headers match, then return a HTTP 304, else send back the cached payload.

We want the cache to timeout every 24 hours, and thus the next call would go to the internal API, which supports ETags. When a client calls with a non-identical ETag or no ETag, the cache is refreshed.

Is this at all possible in APIConnect?