[Koha-bugs] [Bug 12904] Force browser to load new javascript files after upgrade

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12904

Kyle M Hall <kyle at bywatersolutions.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|In Discussion               |Signed Off

--- Comment #5 from Kyle M Hall <kyle at bywatersolutions.com> ---
I think the biggest issue with this approach is it's tied to using Apache,
right? This solution should work with apache, nginx, or whatever crazy way
someone may have Koha up and running. Am I correct?

(In reply to Martin Renvoize from comment #4)
> I've been thinking about this problem for a few yers now.. though never
> gotten around to doing much about it.
> 
> I did at some point start using mod_pagespeed (by google) on a number of our
> server, but this unfortunately led to other problems which I could not
> narrow down to anything but this apache module.
> 
> However, the real piece I wanted was this caching advantage enabled using
> the following filter:
> 
> https://developers.google.com/speed/pagespeed/module/filter-cache-extend
> 
> I'm wondering if we could do somthing similar, either in the Apache config
> itself, or in perl pre apache.
> 
> My thought's were to append a version string within the templates (similar
> to Kyle's approach but within the filename as opposed to a query string) and
> then add some re-write rules in apache to remove the appended string again.
> (I got stuck at the apache re-write rules level.. I've never been especially
> good at them) I did wonder whether we should be appending a hash of the file
> content as opposed to a versions for our version string.. to enable the
> detection of customised changes, but this would obviously add to server load
> too.

-- 
You are receiving this mail because:
You are watching all bug changes.