johan at inceptive.be
Mon Sep 11 07:45:49 UTC 2017
I find the latter a bit strange since that gets injected in a load script or a script tag, and that cannot be cached unless your entire page is cached.
- use some version string in the code base as value in that query parameter such that it is different from the value in the current previous production version (using a version number is most intuitive).
Here is the implementation for that in Seaside:
with the implementation of resourceUrl:version: is:
WAContentElement>>resourceUrl: aString version: versionString
"Concatenates a version string to the resource url.
The version string is put in the GET request's variables list and ignored by the webserver.
Changing the version string can trigger a browser cache refresh when needed."
self url: ((canvas absoluteUrlForResource: aString) addField: versionString)
> On 11 Sep 2017, at 08:41, jtuchel at objektfabrik.de wrote:
> Hi there,
> For many (but not all) users, the changes don't get downloaded for days. They need to go to a page, press the Browser's reload button and from then on they are fine. This is both good to know and bad at the same time for several reasons:
> some users never call and are frustrated
> the number of support cases causes high cost
> Any hints are welcome
> Objektfabrik Joachim Tuchel mailto:jtuchel at objektfabrik.de <mailto:jtuchel at objektfabrik.de>
> Fliederweg 1 http://www.objektfabrik.de <http://www.objektfabrik.de/>
> D-71640 Ludwigsburg http://joachimtuchel.wordpress.com <http://joachimtuchel.wordpress.com/>
> Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside