How to overcome browser caching for replaced files?
Posted: Tue Mar 30, 2010 8:31 pm
We are running CMSms 1.6.6.
I have, several times, replaced a file (.pdf, .xls, at least) that I had previously uploaded with a new version of the file.
When I came to click on the link to it from a Content page, I found that the older version was retrieved.
I tried another browser that I had not used against this site, and it produced the new version; I had also cleared the browser cache earlier, and that solved the problem for me.
However, our clients shouldn't have to know to do that.
Is there any way we can specify in CMSms that a file not be cached?
I'm aware that each content page can be set to cachable (or not); I'm talking about other kinds of files.
Thanks for any help you can provide
I have, several times, replaced a file (.pdf, .xls, at least) that I had previously uploaded with a new version of the file.
When I came to click on the link to it from a Content page, I found that the older version was retrieved.
I tried another browser that I had not used against this site, and it produced the new version; I had also cleared the browser cache earlier, and that solved the problem for me.
However, our clients shouldn't have to know to do that.
Is there any way we can specify in CMSms that a file not be cached?
I'm aware that each content page can be set to cachable (or not); I'm talking about other kinds of files.
Thanks for any help you can provide