[MGNLIMG-112] Ensure that assets and asset renditions are set to cache into the far future Created: 26/Jun/13  Updated: 05/Nov/18

Status: Open
Project: Imaging
Component/s: None
Affects Version/s: None
Fix Version/s: 3.0.x

Type: Bug Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLIMG-105 Ensure that images are set to cache i... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

It must be tested if the following web page resources are in fact using "far future caching" with the appropriate cache busting technique of having the date of modification as part of the file name.
We must confirm that the proper cache headers are on the served files:
http://developer.yahoo.com/blogs/ydn/high-performance-sites-rule-3-add-expires-header-7181.html

It should be tested on:
1. In the assets app in the thumbnails view.
2. In the page editor & page preview that the renditions of images behave this way.

This is critical for page performance and is also evaluated by seo page ranking robots.



 Comments   
Comment by Yassine Elghayabi [ 05/Nov/18 ]

@"Zimmermann Christopher" it would be great if we can have a fingerprints param for getLink in Asset decorator

Thanks

 

Generated at Mon Feb 12 02:12:24 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.