Cache-Control for CDN

If you are using your own Content Delivery Network (CDN) and want to control when your Bynder assets are cached, you can utilize cache-control. By setting cache-control, you can determine how long your Bynder assets are cached. This allows you to specify the expiration time for the cached assets. When a user requests a Bynder asset, it gets cached on your CDN with an expiration time specified through cache-control. This informs the CDN that it should no longer use the cached image once it expires. Instead, the CDN will fetch the latest version of the asset from Bynder.

How to enable this feature in your portal?

Contact your Customer Success Manager to enable this feature in your portal. 

When to Use Cache-Control

When your CDN is not set up by Bynder, but you still want to control when the Bynder assets cached on your CDN expire, you can make use of cache-control.

Limitations

  • Cache-control can only be set up for the original file and cannot be configured for (OTF) derivatives.

  • The configured expiry date will apply to all Bynder assets. It is not possible to set up an expiry time for assets individually.

Updated

Was this article helpful?

0 out of 0 found this helpful

We're sorry to hear that!

Find out more in our community

Have more questions? Find out more in our community