[TAP5-2095] Module assets should not be sent a far-future expires header

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 5.4
• Fix Version/s: 5.4
• Component/s: tapestry-core
• Labels: css
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 15/Mar/13 16:18
• Updated: 16/May/13 23:04
• Resolved: 16/May/13 23:04

Description

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).