move CacheHeadersFilter back to core
-------------------------------------
Key: MAGNOLIA-3171
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3171
Project: Magnolia
Issue Type: Improvement
Affects Versions: 4.3.1
Reporter: Fabrizio Giustina
Assignee: Boris Kraft
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...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
