2 Replies Latest reply on Nov 17, 2017 8:47 AM by gareth.ferrier

    Build number causing caching issues with overlay

    gareth.ferrier Novice

      We've ran into a problem recently where with each new release of our on-premise, overlay based Jive installation that we have to ask users to clear the cache, specifically for JS files.  Looking into it I believe I've found the source of the problem, within the path for resources is the Jive build number, i.e. 1597bde in  https://community.jivesoftware.com/  When we make updates to the overlaid classes/templates/whatever the build number does not change, nor does the generated JS files from soy templates.  Cache-control headers give a 10 year max-age by default, hence the need for the clearing of the cache.  I can see a number of routes to solve, has anyone come across this problem and how did you solve it?