Hello!
In the Tapestry Guide I found this:
-----
Assets are expected to be entirely static (not changing while the
application is deployed). When Tapestry generates a URL for an asset,
either on the classpath or from the context, the URL includes a version
number (as discussed in the previous section). Further, the asset will
get a far future expires header, which will encourage the client browser
to cache the asset.
http://tapestry.apache.org/tapestry5/guide/assets.html
-----
However, I analyzed the network traffic with firebug. All assets are
missing this header and therefore requested every time.
I already saw a tapestry application which set the Expires header to ten
years in the future. What am I doing wrong?
Regards
Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
