Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-340

Images and assets should be cached on client until there is a new version of the asset

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • 5.0
    • None
    • None
    • None

      For M5 Alpha1 we are setting images headers to no cache so we always see the changes when images are edited (http://jira.magnolia-cms.com/browse/MGNLIMG-103) But this is bad for performance.

      First part of this ticket is to remove the no-cache header.
      One implementation strategy for this ticket is to append a querystring to the asset with the modification date (or a key, derived from it) so that the asset can be cached by browser and proxy, but when the asset is modified, then the client loads the new asset.

      Part of the solution may be in Imaging Module, but putting it in here for now.Move ticket if needed.

        Acceptance criteria

              czimmermann Christopher Zimmermann
              czimmermann Christopher Zimmermann
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Bug DoR
                  Task DoD