Betreff: Re: Asset Browser Caching
Tapestry 5.4 itself never sets "Pragma" header (except Kaptcha component,
but it must be included separately and it is set only for actual CAPTCHA
images), and never sets "Cache-Control" to "no-cache, no-store,
must-revalidate" by d
cache, no-store, must-revalidate
> Pragma: no-cache
> ETag: "2f0c65b4"
> Last-Modified: Thu, 21 Apr 2016 10:13:43 GMT
>
> Thanks and best,
> Thilo
>
>
> Von: Cezary Biernacki
> Antworten an: Tapestry users
> Datum: Dienstag, 10. Mai 2016 16:05
>
g, 10. Mai 2016 16:05
An: Tapestry users
Betreff: Re: Asset Browser Caching
Hi,
what Tapestry version are you talking about? In my experience Tapestry is
pretty good at enabling caching assets, with usage of ETags, expiry dates
set for 10 years in the future, and custom URLs to assets. Can you pos
Hi,
what Tapestry version are you talking about? In my experience Tapestry is
pretty good at enabling caching assets, with usage of ETags, expiry dates
set for 10 years in the future, and custom URLs to assets. Can you post
examples of the response headers from your Tapestry that prevent caching?
M
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_CO
