Uploaded image for project: 'Magnolia Resources Module'
  1. Magnolia Resources Module
  2. MGNLRES-144

Implement new origin-based ResourcesServlet

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Major Major
    • 2.4
    • None
    • None

      Should use the new magnolia-resource-loader module from main, and in particular use the LayeredOrigin which implements the unified resource-loading cascade.

      Is expected to replace ClasspathSpool servlet and be similarly mapped to /.resources.

      Random thoughts/things to clarify:

      Processed resources

      • What to do with Resource#modelClass
      • What to do with nested processed resources as sub-nodes (e.g. sample-css)
      • Encourage additional generators as filters (e.g. Sass)
      • see MGNLRES-149

      Security: What should the servlet be allowed to serve?

      • restriction e.g. to serve css/js, not serve ftls, yamls
      • relevant for the whole resource-loading cascade
      • should leave it to URI security where applicable

      Caching

      • apparently ok /.resources is cached in production mode

      Compatibility options

      • Deprecate ResourceLoaders
      • Single resource handle for fresh installs
      • Still support /resources with meaningful warnings otherwise

        Acceptance criteria

          There are no Sub-Tasks for this issue.

              gjoseph Magnolia International
              mgeljic Mikaël Geljić
              Nucleus
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: