[MGNLRES-197] FarFuture caching needs rework of the concept: reference resources and the scriptloadres won't change modification date Created: 04/Jul/13 Updated: 29/Mar/22 Resolved: 21/Aug/15 |
|
| Status: | Closed |
| Project: | Magnolia Resources Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.4 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Christian Ringele | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| 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: | |||||||||||||
| Team: | |||||||||||||
| Description |
|
The STK's javascript loader libraries define by their modification date the time stamp in the far future caching strategy -> the url output of the resource. This means when a resource, any JS for example, gets changed, the time stamp will remain the same because the scrip-loaders didn't change at all. The will still have the same modification date. Possible solution: Becuase there are many modulees involved, resources & STK & cache, I created this issue to main Magnolia project. Also the Url pattern could be optimized. Long ago Aperto wrote a mail to Philipp, explaining problems they have with this URL pattern based on Apache rewrites and VirtualURIMappings. |
| Comments |
| Comment by Christian Ringele [ 26/Nov/13 ] |
|
The included JS resource pints to the scriptloader-libraries.js with an additional resource (print screen Resources-Scriptloader-DefiningThe-URI-AndTimestamp.png): <script src="/demo-project/resources/templating-kit/js/scriptloader-libraries.2013-06-05-18-23-32-183.cache.js" type="text/javascript"></script> The time stamp is determind bz the modification date of the scriptloader-libraries.js resource node's modification date. So four situation when things change that would need a new URI time stamp: All 4 situations have no impact on the time stamp. |
| Comment by Jan Haderka [ 07/Oct/14 ] |
|
Possible solution I can think of
|
| Comment by Jan Haderka [ 21/Aug/15 ] |
|
This issue have been resolved by |