[MAGNOLIA-6709] Enable farFutureCaching also for processed resources. Created: 29/Jun/16 Updated: 22/Apr/20 Resolved: 22/Apr/20 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | resource-loader |
| Affects Version/s: | 5.4.7 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Christian Ringele | Assignee: | Unassigned |
| Resolution: | Outdated | Votes: | 1 |
| Labels: | support | ||
| 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)
|
||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||
| Date of First Response: | |||||
| Description |
|
The processed resources implemented prior Magnolia 5.4.x implemented and provided first the functionality of the 'farFutureCaching'. Since the new resource loading of magnolia 5.4.x, this functionality was removed/not re-implmeneted for the processed resources. This functionality is missed by some clients and also means a removal of existing functionality since Magnolia 4.4. I tried to create a quick patch/workaround, but I failed: |
| Comments |
| Comment by Bence Vass [ 29/Jun/16 ] |
|
addFingerPrint works for JCR resources, if served over /.resources The problem is, that processed resources have to be served over /resources, and only /.resources is recognized as a known resource location by the ResourceLinker. Any fix to this issue should not involve the STK. |
| Comment by Richard Gange [ 22/Apr/20 ] |
|
Since the STK and Processed resources are now considered deprecated I will close this issue. |