[MGNLDAM-568] ImagingBasedAssetRenderer should not add timestamp fingerprint but should rather rely on caching of imaging module Created: 30/Mar/15  Updated: 17/Mar/17  Resolved: 31/Mar/15

Status: Closed
Project: Magnolia DAM Module
Component/s: DAM Imaging
Affects Version/s: None
Fix Version/s: 2.1

Type: Bug Priority: Neutral
Reporter: Philip Mundt Assignee: Philip Mundt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLCACHE-164 Browser cache policy "never" is too b... Closed
causality
is causing MAGNOLIA-6977 CK editor image not updated after edi... Closed
dependency
is depended upon by MTE-11 Text & image component 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:
Epic Link: Extract STK functionality

 Description   

When adding a timestamp fingerprint to an asset link, the info.magnolia.imaging.DefaultImageGenerator will not find the appropriate Node via info.magnolia.imaging.parameters.BinaryNodePathParameterProviderFactory. We should not add timestamps to those links but should rather rely on any info.magnolia.imaging.caching.CachingStrategy from the imaging-module.



 Comments   
Comment by Roman Kovařík [ 16/Mar/17 ]

We should not add timestamps to those links but should rather rely on any info.magnolia.imaging.caching.CachingStrategy from the imaging-module.

This statement doesn't take the browser cache into account at all.

Generated at Mon Feb 12 05:01:08 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.