Details
-
Improvement
-
Resolution: Won't Fix
-
Major
-
None
-
4.3.1
-
None
-
None
Description
talking about the filter described in MAGNOLIA-2011:
the filter for settings headers for client-side cache has nothing to do with server-side caching, so there is no reason why it should be in magnolia-module-cache. It has been moved there incorrectly a long time ago, we should move it back to core.
to refrain:
- the cache module is responsible for storing magnolia generated content and resources server side
- http headers for browser cache is a totally different thing and they are not related at all with server side caching. The SetExpirationHeaders executor tied to the cache module is a big mistake and also the filter has nothing to do with the cache module.
We could rename cacheHeaders filter to HttpHeadersFilter or anything else if the "cache" name makes things confused...
Checklists
Acceptance criteria