For normal assets, the URL directly includes a content hash value. This covers stylesheets, images, fonts, and JavaScript libraries. In addition, assets provide both far-future expires headers and ETags, to assist with caching in the client or intermediate servers.
Modules are a bit different because they can't include the content hash, as the content hash would then be part of the name of the module. So no content hash in module URLs, and no far-future expires header (since an upgrade of the app may change the module). However, there's still ETags support, so most module requests are quickly responded to with a 304 status code. On Fri, Mar 14, 2014 at 9:35 AM, Luke Wilson-Mawer < lukewilsonma...@gmail.com> wrote: > In previous version the asset URLs contained the version, so they would > change each time the version changed. In 5.4 this doesn't seem to be the > case. > > Am I mistaken? If not, is this by design? And what's to stop assets being > cached between releases of different versions of the software? > > Kind regards, > > Luke > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
