[
https://issues.apache.org/jira/browse/TAPESTRY-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-2159.
------------------------------------------
Resolution: Fixed
Fix Version/s: (was: 5.1)
5.0.12
Assignee: Howard M. Lewis Ship
This was bundled with some other changes.
> YSlow Recommendation: Version bundled javascript and use far-future expires
> header
> ----------------------------------------------------------------------------------
>
> Key: TAPESTRY-2159
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2159
> Project: Tapestry
> Issue Type: Improvement
> Affects Versions: 5.0.10
> Environment: Any
> Reporter: Ernest Monklitch
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.12
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
