Caching issue with WebHelp

This forum is for all Flare issues related to the HTML5, WebHelp, WebHelp Plus, and Adobe Air Targets

Caching issue with WebHelp

Postby jknasinski on Thu Sep 03, 2015 5:09 am

My dev team recently reported a caching issue with webhelp. They say that at times when an updated webhelp project is deployed, the browser's cache has to be cleared in order for the correct, most recent files to be displayed. We hadn't noticed this behavior before; just in the last couple of months.
The dev team created a small web.config file that they want me to include with my webhelp projects from now on that they say will fix the caching issue.
Has anyone else heard of this type of issue or dealt with it?
We support various browsers from IE to Chrome and Firefox. The same issue hasn't been reported on one of our other webhelp projects. Both are standard webhelp built with Flare 11.

Instead of using their small web.config file and having to remember each time I deploy to include that file, I'm proposing to just add the following in my targets (target > Advanced tab > Add meta tags to content):

<META http-equiv="Cache-Control" content="no-cache" />
<META HTTP-EQUIV="Pragma" CONTENT="no-cache" />
<META HTTP-EQUIV="Expires" CONTENT="-1" />

Comments?
jknasinski
Propeller Head
 
Posts: 36
Joined: Tue Jul 10, 2012 9:31 am
Location: Milwaukee Wisconsin

Re: Caching issue with WebHelp

Postby mjpitman on Thu Jan 24, 2019 4:20 am

Hi jknasinski,

I've encountered an issue recently after updating the project's headers.h file, where the published webhelp would not catch new ids unless you clear the browser's cache.

Conscious of the age of this thread, but did the idea you proposed clear up this issue, or did you find an alternative solution?
mjpitman
Jr. Propeller Head
 
Posts: 2
Joined: Thu Oct 18, 2018 6:41 am

Re: Caching issue with WebHelp

Postby daphna on Wed Dec 18, 2019 7:57 am

We are constantly struggling with this. Adding the no-cache rule into the metadata does not help. We have been back and forth for years.

My IT resources has asked to revisit...we have talked with MC support before and the answer is the no-cache rule in the metadata. The IT resource has been doing some research and has run across numerous articles that essentially say the same thing: “HTML5 does not include the cache-control or Pragma in meta elements, which is what MC and MC Forum solution is. For example: https://stackoverflow.com/questions/152 ... om-caching

This issues is very frustrating. Any thoughts or suggestion would be much appreciated.
daphna
Propeller Head
 
Posts: 33
Joined: Fri Feb 03, 2006 1:00 pm


Return to Web-based Outputs

Who is online

Users browsing this forum: No registered users and 4 guests