Uploaded image for project: 'Advanced Cache'
  1. Advanced Cache
  2. MGNLADVCACHE-76

A explicit direct area/component rendering can save the fragment with a wrong TTL

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Neutral
    • None
    • 1.7.5
    • DCP
    • None

    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.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              Unassigned Unassigned
              rkovarik Roman Kovařík
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Checklists

                  Bug DoR
                  Task DoD