I see how this can be a problem, but I don't want users to have to download all css and all js on each request. I _want_ caching - most of the time.
chris Davor Hrg (JIRA) wrote: > [ > https://issues.apache.org/jira/browse/TAPESTRY-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571720#action_12571720 > ] > > Davor Hrg commented on TAPESTRY-2159: > ------------------------------------- > > Unfortunately, it is the only way make browser reload files. > > Firefox for example will stop asking server(If-Modified-Since) for changes if > a .js file > has not changed for a while. > > I've experienced this on large project on daily basis, > so I've started to incorporate file timestamp into url > to make sure it is reloaded on every change. > > it is even worse for .css files I have to clear cache manually often to get > fresh css. > > adding timestamp to js url and css url is not invasive towards developer > and is guaranteed to refresh every time :) > > > > > >> Version bundled javascript >> -------------------------- >> >> Key: TAPESTRY-2159 >> URL: https://issues.apache.org/jira/browse/TAPESTRY-2159 >> Project: Tapestry >> Issue Type: Improvement >> Affects Versions: 5.0.10 >> Environment: Any >> Reporter: Ernest Monklitch >> Fix For: 5.1 >> >> >> Jesse Kuhnert has already implemented this in T4. (Jira issue TAPESTRY-2122.) >> Prevents client side errors that occur if user doesn't flush browser's cache >> between Tapestry upgrades. (And javascript has changed.) >> > >
