[MGNLADVCACHE-85] Support ETag configurable in Advanced cache policies Created: 23/Feb/17  Updated: 11/Jul/19

Status: Open
Project: Advanced Cache
Component/s: core
Affects Version/s: 1.8.2
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Viet Nguyen Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
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   

Thanks to buf481 suggestion in MGNLAVERS-97, supporting ETag configurable in advanced cache policies module would be an interesting topic which has been mentioned shortly here in our Cache improvements concept page.

It would be nice to have it configurable in the cache configuration. The ETag could be an option that could be enabled in the cache policy and directly linked to the records that is stored there (and hence flushed when new content is activated) or be a separate area of configurable caching (similar to the browser cache node) and generated from lastModifed+uuid.


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