[MGNLIMG-105] Ensure that images are set to cache into the far future Created: 03/Jan/13 Updated: 26/Jun/13 Resolved: 26/Jun/13 |
|
| Status: | Closed |
| Project: | Imaging |
| Component/s: | None |
| Affects Version/s: | 3.0 |
| Fix Version/s: | 3.0 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| 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)
|
||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||
| Description |
|
now that we have a fingerprint technology which inserts the modification date into an images url, image caching should be set to the far future. |
| Comments |
| Comment by Christopher Zimmermann [ 03/Jan/13 ] |
|
103 is now out of date and we should ensure that caching is set for future. |
| Comment by Magnolia International [ 16/Jan/13 ] |
|
Here's a bit of a conversation I've had with Espen and Tobias on Hipchat
(although, IIRC, mgnlCK is "current timestamp" - whereas this "fingerprint" uses the image's modification date?) What I don't understand is that the imaging module already takes care of that - if source was modified, If images generated for admin central need to be behave differently from a caching perspective, why not configure a different servlet, and/or play with the settings of the cache module ? |
| Comment by Christopher Zimmermann [ 26/Jun/13 ] |
|
Removed no-cache http headers in the Imaging servlet. |