Cache busting

volume_up

A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.

volume_up

A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.

Home / Forums / Developers (Main Products) Forum / CMS 7.5 - 11 /

Cache busting

Thomas Dane

Vote:

expand_less 0 expand_more

We have noticed that images uploaded via the CMS are served with an Expires header. Currently we use the default value of 12 hours. We have encountered a problem where an Editor changes and image but re-uploads it with the same name.

This means the browser does not re-request the asset. The ETag does not change.

Is it possible to append some hash or GUID to Episerver images so that they have a unique name on each change?

#173913

Jan 12, 2017 15:18

valdis

Vote:

expand_less 0 expand_more

We use Mads Kristensen approach (fingerprint) for bursting cache for static client side resources - http://madskristensen.net/post/cache-busting-in-aspnet

Maybe similar approach could be used for ages as well - like adding query string parameters at the end?! To generate unique query string you can use last modified date from content data..

Not sure if that's the best approach tho

#174362

Jan 25, 2017 8:13

Thomas Dane

Vote:

expand_less 0 expand_more

Thanks Valdis! It worked.

#175173

Feb 14, 2017 14:22

error This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.