How to ensure users see latest version and not a cached version?

Will someone assist me in developing a workflow to make sure my users see the latest revision of  a project and not a cached version on their local computer?

How do I beta test a project with them? I want to email a single url that remains constant throughout the development cycle. What I am finding is that after I make revisions and upload a revised project, my users continue to see the old version. I understand clearing the local cache solves this, but it isn't practical for me. I often ask a group of administrators to explore the project to get feedback. To try and talk them through clearing their browser cache with different OSes and browsers, is just not good use of their time (nor will they have the patience for it). Users also bookmark the link I send them, so creating a new url each time is problematic since I can never be sure how they are accessing the project.

I'm hoping someone has figured out a work around. Any advice? Thanks. 

6 Replies
Will Findlay

Good question! It depends on the browser.  Do your users always use a single browser? This page gives some simple suggestions:

but I've heard Ctrl + F5 is not the silver bullet for Internet Explorer:



Jim Murtagh

Great idea. I'll pursue this. Your post led me to this snippet of code that I will try to add to Storyline's output. You could be on to something. Thanks.

<META HTTP-EQUIV="Pragma" CONTENT="no-cache">