Uploaded image for project: 'Cache Modules'
  1. Cache Modules
  2. MGNLCACHE-125

Cache header negotiation does not work for first request after cache flush

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Critical
    • 5.3.3, 5.4.3
    • 5.3.2
    • cache core
    • Kromeriz 17
    • 3

    Description

      We've got trouble with different cache headers for the same page request. Sometimes we saw the correct no-cache headers and sometimes the default cache configuration headers.

      The pattern is that every first request after a cache flush will use the configured browser cache policies and overwrite the cache headers set by code. See Cache header negotiation

      The reason seems to be that missing cache entries will be stored as uncacheable cache entries in the cache. And then the cache will bypass such cache entry requests. But for the first request the browser cache policies will overwrite the existing cache headers.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                rkovarik Roman Kovařík
                frank.sommer Frank Sommer
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Bug DoR
                    Task DoD

                    Time Tracking

                      Estimated:
                      Original Estimate - Not Specified
                      Not Specified
                      Remaining:
                      Remaining Estimate - 0d
                      0d
                      Logged:
                      Time Spent - 40m
                      40m