How does browser cache work?
When the browser sends a request to the mid tier server, the server controls the response that goes back to the browser. Depending on the type of request, the mid tier server determines whether to send a Cache-Control header in the response.
Types of requests
The mid tier server controls browser cache based on the following types of requests:
- Dynamic — These requests fetch dynamic data, such as records, from the BMC Remedy AR System database, and thus are not cached on the browser.
When a new BMC Remedy Mid Tier patch or hotfix is applied, the content of these files might change.
The content of these requests can change when changes are made to form definitions or workflows.
Modifying the cache expiry settings
As an administrator, you can adjust the cache expiry settings from the config.properties file located at /midTierInstallDir/WEB-INF/classes/. The browser uses these settings to determine how long the content is cached.
- Resources — The default setting for this request type is 86400 seconds (1 day). To change the cache expiry settings for this request type, modify the following entry: