Hi all, We use Tapestry mainly for internal applications. We have users working from places with very limited bandwidth (use Chrome’s „Good 2G“ network throttling to get an idea). It seems, the headers sent by Tapestry prevent the browser from caching assets. I modified OMIT_EXPIRATION_CACHE_CONTROL_HEADER, but without success (it seems, this settings is only used for assets without a checksum path). Production mode is enabled. I couldn’t find an issue in JIRA related to this problem, so maybe we’re doing something wrong here. We use a modified AssetRequestHandler to stream webjar assets from T5 submodules, but the problem is the same for core.js or any other directly loaded asset.
All inputs are welcome! Thanks and best, Thilo Thilo Tanner Technology Lead Direct +41 43 300 54 42 <tel:+41%2043%20300%2054%2042> Mobile +41 795064636 <tel:+41%20795064636> thilo.tan...@reprisk.com <mailto:thilo.tan...@reprisk.com> www.reprisk.com <https://www.reprisk.com> RepRisk AG Stampfenbachstrasse 42, 8006 Zürich, Switzerland Office +41 43 300 54 40 Fax +41 43 300 54 46 [RepRisk Logo] <https://www.reprisk.com>
