Probably some of you have noticed that Chrome has this habit of caching media assets in a rather aggressive way, showing an older version even when a file is updated.
Does anyone have a solution to forcing the browser to detect or at least not cache the Media assets on Umbraco?
Note: we were using the trick of adding a parameter with ? and a time stamp but since moving to Azure blob this does not work, files get "zipped" by Azure blob. Weird huh.
Follow up to this post from January, there is a fix using a modified web.config in the Media folder. Simply add portion inside and including httpProtocol:
Browser caching PDFs
Hi everyone,
Probably some of you have noticed that Chrome has this habit of caching media assets in a rather aggressive way, showing an older version even when a file is updated.
Does anyone have a solution to forcing the browser to detect or at least not cache the Media assets on Umbraco?
Note: we were using the trick of adding a parameter with ? and a time stamp but since moving to Azure blob this does not work, files get "zipped" by Azure blob. Weird huh.
Thank you! Genc
Follow up to this post from January, there is a fix using a modified web.config in the Media folder. Simply add portion inside and including httpProtocol:
Now Chrome will not cache the PDFs. Seems to work. Thx!
the simple way is to change URL or query string, it doen't make sence disable cache for client
Problem is using query string on Azure Blob storage with Umbrao Cloud is generating a zip file.
Here try it yourself, this should be an xlsx file: link
We can't change all the URLs, some we need to keep consistent. So URL change is not an option either.
What is the problem with not caching Media items like PDFs or XLSs? We specifically want to be sure the user always gets the latest version.
Any solution for this?
is working on a reply...