[MAGNOLIA-2860] cache: the cache key should take parameters into account Created: 03/Sep/09  Updated: 23/Jan/13  Resolved: 10/Mar/10

Status: Closed
Project: Magnolia
Component/s: cache
Affects Version/s: None
Fix Version/s: 4.3

Type: Improvement Priority: Major
Reporter: Philipp Bärfuss Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLCACHE-37 Cache configuration should be simplified Closed
is related to MAGNOLIA-2849 Cache: cache keys based on host names... Closed
is related to MAGNOLIA-3074 cache: the key should contain current... 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)

 Description   

If the cache key would take the request parameters into account one could simply steer by configuration where one wants caching despite the fact that parameters are present.

At the moment, the cache can be configured to cache (or not cache) when request parameters are present; but if one wants to cache when parameters are present, the cache key is still the same as if they were not present, i.e rendering that configuration option useless or confusing at best.


Generated at Mon Feb 12 03:40:49 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.