[MGNLSTK-714] resources: use modification date to apply the far future caching strategy Created: 28/Nov/10 Updated: 03/Aug/11 Resolved: 29/Nov/10 |
|
| Status: | Closed |
| Project: | Magnolia Standard Templating Kit (closed) |
| Component/s: | base system |
| Affects Version/s: | None |
| Fix Version/s: | 1.4 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Philipp Bärfuss |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Template: |
|
||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||
| Description |
|
use the modification date to create a link of the format: /resources/path/style.timestamp.cache.css the new default browser cache configuration will set a far future (one year) expiration header. |
| Comments |
| Comment by Philipp Bärfuss [ 29/Nov/10 ] |
|
Resource class has a farFutureCachable property. If set to true the class uses the uri to repository mapping to get the content and reads its creation/modification date. |