A request like below can be cached like any HTTP request. This means that an identical request can be retrieved from cache, instead of processing the request on server side to get current data. This cache can occur on the client browser or in network devices between client device and Qlik Sense server.
https://my-qlik-server.com/api/hub/v0/apps
By making each request unique, it is possible to bust the cache and enforce that request are sent to origin server. The cachebust URL parameter allows Qlik Sense client to ensure that a request is unique by adding a unique number in the URL.
The below two requests are cached like any other HTTP request. They are completely different request due to the cachebust parameter, and thus avoid the logically equal request https://my-qlik-server.com/api/hub/v0/apps to return a cached response.
https://my-qlik-server.com/api/hub/v0/apps?cachebust=1517220328885
https://my-qlik-server.com/api/hub/v0/apps?cachebust=9851452037385
This technique is used by Qlik Sense for dynamic requests that require new updated directly form server side. Requests for static content (such as JS, CSS or image files), information can be retrieved from cache if previously available.
Environment:
Qlik Sense Enterprise on Windows
