[MGNLCACHE-145] Provide a local scoped component which is able to influence caching Created: 14/Sep/16  Updated: 09/Feb/17  Resolved: 28/Dec/16

Status: Closed
Project: Cache Modules
Component/s: cache core
Affects Version/s: None
Fix Version/s: 5.5

Type: Improvement Priority: Neutral
Reporter: Roman Kovařík Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MSITEMESH-43 Invalid security token if fragment is... Closed
supersession
supersedes MGNLCACHE-39 Provide Util method to prevent reques... Closed
is superseded by MSITEMESH-13 Don't create a new connection for fra... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Sprint: Kromeriz 61
Story Points: 2

 Description   

Provide a local scope component to share cache policy result instead of a custom request attribute (you don't need to know the name of the request attribute anymore, just inject Provider<CachePolicyResultProvider>)
-We can provide custom cache key generators provided via X-Magnolia-Cache header has to be registered.-
-To prevent spoofed request, we use security tokens registry in the site mesh module. This doesn't work with multiple public instances.-
-Drop STR in favour of registration of cache key generators in the cache module-



 Comments   
Comment by Roman Kovařík [ 16/Sep/16 ]
  • custom cache key generator classes (e.g those used in fragment definitions) has to be registered under /modules/cache/config/contentCaching/<cache-name>/cachePolicy/registeredCacheKeyGenerators for security reasons.
    e.g. /modules/cache/config/contentCaching/defaultPageCache/cachePolicy/registeredCacheKeyGenerators/0=my.custom.key.generator
Comment by Roman Kovařík [ 27/Sep/16 ]

Reopened: registering of key generators to be reverted.

Comment by Roman Kovařík [ 16/Dec/16 ]

This ticket won't be done since we don't need a registration of cache key generators since we use fragment for fragment requests in the site mesh module.

Generated at Sun Feb 11 23:52:39 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.