-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
-
Empty show more show less
-
Yes
Currently, "header negotiation" lets page components set Cache* headers, which in turns sets the TTL of a cache entry to 0. The Store CacheExecutor then sees this, "replays" the cache entry immediately and discards it (rather than putting it in the cache and letting the useCache executor handle it)
While implementing MGNLPN-112, we realized that we could instead store a "marker" entry in the cache, and on further access to such entry, the cache policy could simply instruct the cache to be bypassed.
- is depended upon by
-
MGNLADVCACHE-29 EagerRecacheCachePolicy doesn't take UncacheableEntries into account
- Closed
-
MGNLPN-189 Remove personalisation-specific cache configuration
- Closed
- is related to
-
MGNLCACHE-78 Move store caching configuration into cachePolicy
- Closed
- supersedes
-
MGNLPN-112 Bypass cache for personalized pages
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...