-
New Feature
-
Resolution: Fixed
-
Major
-
None
-
None
-
-
Empty show more show less
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#modelClassWhat 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
- depends upon
-
MGNLRES-152 Generate links to resources, and use selectors with ~ to generate farFutureCaching URLs for resources
- Closed
-
MAGNOLIA-6218 Expose resource's last modification date
- Closed
-
MAGNOLIA-6219 ClasspathOrigin: filter resources out; expose mgnl-resources
- Closed
-
MAGNOLIA-6220 Resources: clarify pathPattern usage and Predicates in Origin methods
- Closed
- is causing
-
MULTISITE-44 Review default bypasses for CrossSiteSecurityFilter
- Open
- is depended upon by
-
MAGNOLIA-6229 Deprecate ClasspathSpool servlet
- Closed
- is superseded by
-
MGNLRES-149 Concept for supporting processing resources served via /.resources
- Closed
- supersedes
-
MGNLRES-136 Add ability to serve resources directly from filesystem
- Closed