You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2013/03/15 17:20:13 UTC
[jira] [Created] (TAP5-2095) Module assets should not be sent a
far-future expires header
Howard M. Lewis Ship created TAP5-2095:
------------------------------------------
Summary: Module assets should not be sent a far-future expires header
Key: TAP5-2095
URL: https://issues.apache.org/jira/browse/TAP5-2095
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.4
Reporter: Howard M. Lewis Ship
Priority: Blocker
Modules should no longer include either the application version number in the URL, or include a far-future expires header. Instead, module requests and response should support HTTP Etags (http://en.wikipedia.org/wiki/HTTP_ETag).
The reasoning behind abandoning the application version number is that it relies on the developer to know when to change the version number (well, basically on every redeployment), and it invalidates all assets (this it the case in Tapestry 5.3).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira