[TAP5-90] Context assets should be versioned and provided with a far future expires header, just like classpath assets

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.0.15
• Fix Version/s: 5.1.0.0
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 22/Apr/08 17:12
• Updated: 08/Jan/09 06:44
• Resolved: 08/Jan/09 06:44

Description

This is as-per YSlow recommendations, assets in the context (i.e., the context: asset prefix) should be treated like classpath: assets; the URL sent to the browser should reflect a version number (defined by the application) and the files should be given a far future expiration date.

So the URL might be "/app-assets/1.2.3/images/logo.gif" for a file referenced as "context:images/logo.gif". The application would define the version number. It would be the developer's responsibility to advance the version number whenever the context files change (i.e., on each new deployment of the application).