Caching

CDN caching accelerates the loading times of assets as it allows to host them as close as possible to your end users. By using CDN caching, your ensure maximum performance of your website. You can define the max-age and s-maxage attributes in the Cache-Control HTTP Header of assets delivered by Filerobot to control the caching behavior.

When this cache expired, the asset will be requested from the origin and the new assets delivered to the client.

We recommend using Invalidation if you need to refresh your assets as it will not impact your CDN cache-hit ratio.

The caching period settings can be customized in the Filerobot DAM Console settings:

Photo alt \#responsive

directive description
max-age The time in seconds that the asset is allowed to be re-used.
For instance, max-age=36000 indicates that an asset remains in the browser cache for the next 36 000 seconds (10 hours).
s-maxage This directive applies only to the caching in CDN. To maximise performance,
we recommend you set a high value here and invalidate assets when needed.

Asset caching settings

You can define the caching interval of a specific asset by setting the ci_cache=X URL parameter of the asset where X is the interval in seconds.

/docs/bag.jpg?ci_cache=500

This will override the max-age and s-maxage attributes only for this asset.

Automatic origin image refresh

Photo alt \#responsive

If you need to use a very small caching interval for a specific image (for example, snapshots from a live webcam or a specific chart with dynamically changing contents), you need to change the Automatic origin image refresh setting in your DAM Console. This tells our resizing servers to update all origin images after this interval has expired.

Please note that the Automatic origin image refresh value affects all URLs using your token. This will not change your CDN cache but after this interval expires, the origin image will be fetched by our resizing servers from your storage on every new operation or filter.