| Time |
Nick |
Message |
| 01:39 |
|
sandbergja joined #evergreen |
| 06:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 10:44 |
|
jvwoolf joined #evergreen |
| 10:51 |
dbs |
Weird, back in http://irc.evergreen-ils.org/evergreen/2019-11-18#i_426876 jeff said upup should automatically load new resources based on expire time |
| 10:52 |
dbs |
But I just logged into the staff client on a computer I hadn't used for days and got a white screen of death until I refreshed manually (used Network dev tools panel + disable cache to reload the page) |
| 10:54 |
dbs |
text/html requests show an expire time of 18 hours, per the example config |
| 10:56 |
dbs |
but https://laurentian.concat.ca/js/ui/default/staff/build/js/core.bundle.js and https://laurentian.concat.ca/IDL2js?locale=en-US also have an expire time of 1 year, also per the example config |
| 10:57 |
dbs |
This seems like a non-optimal default, given that they were set so long based on the assumption that the cache-busting param would be in play |
| 11:00 |
dbs |
(per https://github.com/evergreen-library-system/Evergreen/blob/master/Open-ILS/examples/apache_24/eg.conf.in#L90 ) |
| 11:01 |
* dbs |
resets his expire times to 4 hours across the board for everything for now |
| 11:32 |
|
sandbergja joined #evergreen |
| 12:10 |
|
jvwoolf left #evergreen |
| 12:37 |
jeff |
the upup cache-version value is set to the current day at the tt2 template level, so if your browser loaded a fresh copy of that html (which it probably did, if it was set to cache for 18 hours and had been not used for days). |
| 12:38 |
jeff |
that should have caused upup to re-fetch what it considers assets "for offline access". |
| 12:38 |
jeff |
but i don't think it has any overall effect on other resources cached by the browser for the origin in question. |
| 12:38 |
jeff |
even if it's within the upup "scope" |
| 12:39 |
jeff |
that comment in the apache config for "to force browsers to reload them immediately" does seem to assume that the output of a template using cache.tt2 would not itself be cached... that might be true now that i say it. |
| 12:41 |
jeff |
since we set "access plus 5 seconds" as the ExpiresByType for text/html in <Location /eg/opac> (in eg_vhost.conf) |
| 12:41 |
jeff |
(then there's the internal template toolkit cache on disk...) |
| 12:45 |
jeff |
...but in the case of both URLs in your example of those having a one year expiry, they should be already in the assets array for upup, so they'd in theory be re-fetched. |
| 13:06 |
jeff |
(hrm.) |
| 13:30 |
|
sandbergja joined #evergreen |
| 16:08 |
|
sandbergja joined #evergreen |
| 16:17 |
|
sandbergja joined #evergreen |
| 16:36 |
|
sandbergja joined #evergreen |
| 18:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 18:38 |
|
stephengwills joined #evergreen |
| 21:08 |
|
Christineb joined #evergreen |
| 22:23 |
|
sandbergja joined #evergreen |
