Skip to main content
Russ Ortisi
Russ Ortisi
Inspiring
February 14, 2018
Answered

Is it Possible to have the API Manager Cache Results when Query String Arguments Are Passed?

  • February 14, 2018
  • 1 reply
  • 378 views

I have a resource I have set up in one of my APIs, which the user may call with different arguments to augment the result set. For example, the user may want to pull back all of the objects in the database. In this case, no arguments are sent and all items are returned. But, they may also want a specific category and they may want to limit the results to a certain number. If they provide a query string argument for category and another for limit, the web service responds accordingly. They may also want to retrieve just one record. If they pass an ID for the record, the web service just pulls back that one record.

The trouble comes in when I implement caching for the API. After the response is cached for any set of arguments, it doesn't matter if I change the arguments, it still only pulls back the cached result set it originally returned when the cache was set.

Is there any way I can get it to behave more like query caching in ColdFusion, where it will cache separate result sets when different arguments are passed?

UPDATE: After looking more closely at RESTful standards and practices, I decided to give this a try as a POST method, passing a JSON string with the filter data I need for this query. I thought that might help with the caching issue, but it doesn't seem to have made a difference. Whatever parameters I send in JSON, it sends back the data it cached on the first attempt to the endpoint.

Any help or suggestions are appreciated here.

This topic has been closed for replies.
Correct answer Russ Ortisi

I've got this one figured out. There are a couple of things to keep in mind.

1. When caching is set at the resource level and parameters are sent via the URL, it doesn't seem to cache different results based on the parameters.

2. When caching is set at both the query level in your CF code and in the API Manager, the results can vary and be unpredictable.

3. If you remove caching at the query level in your CF code, and only have it enabled in the API Manager, it works properly when:

3a. You define a variable value for the resource, such as /{id} and then pass the ID - it will return proper results

3b. You use a POST resource to pass unpredictable filter data via JSON

In my case, my users can filter the listing by category and whether the item is marked as "featured", and they are also able to specify a limit to the number of records which come back. None of these is required, so they could send whichever combination of these filters they choose. And now the caching is working as we would expect, so that's a win.

1 reply

Russ Ortisi
Russ OrtisiAuthorCorrect answer
Inspiring
February 19, 2018

I've got this one figured out. There are a couple of things to keep in mind.

1. When caching is set at the resource level and parameters are sent via the URL, it doesn't seem to cache different results based on the parameters.

2. When caching is set at both the query level in your CF code and in the API Manager, the results can vary and be unpredictable.

3. If you remove caching at the query level in your CF code, and only have it enabled in the API Manager, it works properly when:

3a. You define a variable value for the resource, such as /{id} and then pass the ID - it will return proper results

3b. You use a POST resource to pass unpredictable filter data via JSON

In my case, my users can filter the listing by category and whether the item is marked as "featured", and they are also able to specify a limit to the number of records which come back. None of these is required, so they could send whichever combination of these filters they choose. And now the caching is working as we would expect, so that's a win.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices