Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
5.0.10
-
None
-
None
-
Any
Description
Jesse Kuhnert has already implemented this in T4. (Jira issue TAPESTRY-2122.)
Prevents client side errors that occur if user doesn't flush browser's cache between Tapestry upgrades. (And javascript has changed.)
See: http://developer.yahoo.com/performance/rules.html#expires
This really applies to classpath resources. Context resources can also be versioned and (via some kind of servlet container ju-ju) hack the expires header ... but that's an application development and deployment issue seperate from Tapestry.
Part of this requires that the Tapestry release number be available and incorporated into the mapped path for the classpath asset. See TAPESTRY-2231.