[MGNLADVCACHE-76] A explicit direct area/component rendering can save the fragment with a wrong TTL Created: 17/Aug/16  Updated: 11/Jul/19

Status: Open
Project: Advanced Cache
Component/s: DCP
Affects Version/s: 1.7.5
Fix Version/s: None

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

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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

To reproduce:

  1. Configure a dynamic component with TTL=0.
  2. Render the component manually from the browser /page/component
  3. The component is saved in cache with TTL=-1
  4. Request whole page twice so the dynamic component is injected.
  5. The cached fragment from the point 1 is used although is should not be cached.

Solution: use non default cache key generator in the dynamic fragment definition so fragments do not interfere with direct component/area rendering.


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