Chrome Caching - Same file name

  • 1
  • Problem
  • Updated 2 years ago
  • Solved
Archived and Closed

This conversation is no longer open for comments or replies and is no longer visible to community members.

We are using Adobe Captivate to publish content as an HTML image slideshow, stored on a local IIS web server. Captivate tends to re-use image names, and Chrome is caching these images for days at a time before updating to the new ones. The website widget is set to refresh every 30 minutes.

Our staff (K-12 Clerical) publish new content daily, and sometimes multiple times throughout the day. At the moment, we are restarting the players on each display whenever we need to clear the cache. This is working for the Chrome app player, but not the native Linux player. Both are running Lubuntu 15.04 32bit.

I can replicate this issue on a workstation in Chrome, viewing the content from the web server as the players are, I get the same cached content until I clear the cache. Using Internet Explorer, with "Check for newer versions of stores webpages, everytime" checked, new content is shown right away.

I've read the suggestion to use different file names, but this isn't feasible for our staff, as they are very time limited. The process we have now for publishing content is very quick.

Any suggestions?
Photo of Eric Giesbrecht

Eric Giesbrecht

  • 184 Points 100 badge 2x thumb

Posted 3 years ago

  • 1
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb
Eric,
Is the web page widget the only thing contained in the presentation? If so, have you tried scheduling the URL directly, without even using Editor? You can just go to schedules.risevision.com, access the schedule, remove the current presentation, then click "Add Playlist Item", and select "URL". Paste your website URL directly in there.

Let me know if this works!
Photo of Eric Giesbrecht

Eric Giesbrecht

  • 184 Points 100 badge 2x thumb
The web page is the only item in the presentation, I'll give this a try and let you know, thanks.
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb
Please do, I'm curious to know the results ;)
Photo of Eric Giesbrecht

Eric Giesbrecht

  • 184 Points 100 badge 2x thumb
No change, still caching. I've been trying to replicate this issue, and it seems to only occur when content has been playing for a period of time, longer than an hour maybe, I'll do some more testing.  When changing one slide on and off a few times quickly, the content updates as desired.
Photo of Eric Giesbrecht

Eric Giesbrecht

  • 184 Points 100 badge 2x thumb
It does look like our index.html is being cached, and not updated on refresh. Will investigate this as well.
Photo of Eric Giesbrecht

Eric Giesbrecht

  • 184 Points 100 badge 2x thumb
May have found a fix, I've set our IIS HTTP expires response header to expire immediately. Will update with results.
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb
Let us know! This is a bit outside of my wheelhouse since it's all locally hosted content.
Photo of Eric Giesbrecht

Eric Giesbrecht

  • 184 Points 100 badge 2x thumb
This is resolved now, the change to the IIS HTTP expires response header (immediately) was the solution.
Photo of Darius - PRODO.us

Darius - PRODO.us, Champion

  • 26,850 Points 20k badge 2x thumb
Eric,

Could you please explain how exactly did you do this. I am getting the same problem and I am looking for a permanent solution to this instead of clearing the cache.
Photo of Eric Giesbrecht

Eric Giesbrecht

  • 72 Points
Assuming you're using IIS for your web server:

This is using server 2012 r2 & IIS 8.5.

- In IIS manager, select your site and go to "HTTP Response Headers".
- Under actions, go to "Set Common Headers".
- Check "Expire Web content" and select "Immediately".
Photo of Robb

Robb, Official Rep

  • 76,676 Points 50k badge 2x thumb
Thanks for that answer Eric!