Uploaded image for project: 'Magnolia Multisite Module'
  1. Magnolia Multisite Module
  2. MULTISITE-177

Allow custom cache keys in the MultiSiteManager

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Unresolved
    • Neutral
    • None
    • 2.1.2
    • None

    Description

      Currently MultiSiteManager uses domain + uri as the key for the internal site cache. With the addition of Live Copy there might be use cases where you have multiple trees being served on the same domain. Without the ability to customize the key it can create conflicts when trying to request content which might be the same in domain and uri but different in other aspects.

      Consider a rest call to a workspace which uses a single-tree-multi-language configuration:

      https://www.site.com/.rest/endpointPath/{path}?lang=de
      https://www.site.com/.rest/endpointPath/{path}?lang=en
      

      An improvement would be to take the same approach as the Cache module where the entire AggregationState object is passed to a cache key generator. The domain and uri would still be available through the AggState object but would also allow an easier entry point for custom keys. Currently in the MultiSiteFilter we already are getting this data from the AggState.

      Notes
      The multisite module needs a new configuration for the cache key generator class.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              Unassigned Unassigned
              rgange Richard Gange
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Checklists

                  Task DoD