Details
-
New Feature
-
Resolution: Fixed
-
Critical
-
None
-
None
-
-
Empty show more show less
Description
One issue to rule them all.
Checklists
Attachments
Issue Links
- is related to
-
MAGNOLIA-2056 Activation: 401s are ignored or not reported when activating a single page
-
- Closed
-
-
MAGNOLIA-1995 Default cache implementation ignores compression type from configuration
-
- Closed
-
-
MAGNOLIA-2057 Initial download cancelation leads to corrupt cache file
-
- Closed
-
-
MAGNOLIA-2104 cache: ehcache ignores the configured cache directory
-
- Closed
-
-
MAGNOLIA-2107 cache: ehcache does not set the modification date
-
- Closed
-
-
MAGNOLIA-2037 Add the new CacheHeadersFilter to the default filter chain
-
- Closed
-
-
MAGNOLIA-1704 CacheKey should be calculated by CacheFilter instead of CacheManager
-
- Closed
-
-
MAGNOLIA-1771 cache: move deny configuration to the filter or support a per filter configuration
-
- Closed
-
-
MAGNOLIA-1892 cache: decoupled cache flushing
-
- Closed
-
-
MAGNOLIA-1931 cache: unwire observation and use content2bean
-
- Closed
-
-
MAGNOLIA-2023 filters: cache should be infront of i18n
-
- Closed
-
-
MAGNOLIA-2105 cache: CacheManager is not configurable
-
- Closed
-
-
MAGNOLIA-2110 cache: set modification date on first request
-
- Closed
-
-
MAGNOLIA-2157 cache: wrong content length for resource streamed from docroot
-
- Closed
-
-
MAGNOLIA-1913 Content-Length not set properly for top site url
-
- Closed
-
-
MAGNOLIA-2177 When caching (1st request), we're always serving the gzip'd content, even if the client does not accept gzip encoding
-
- Closed
-
-
MAGNOLIA-2129 Cache : RenderingFilter should not flush when caching is enabled
-
- Closed
-
-
MAGNOLIA-2184 Incorrect flush policy renders instance unusable
-
- Closed
-
-
MAGNOLIA-2187 Make different possible Cache policy behaviours configurable outside of CacheFilter
-
- Closed
-