Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-22569

Removed Location still shows on frontend until http cache expires

    Details

      Description

      when any object has multiple locations, while the header Age: does not reach the s-maxage: a location is served from caches, even if it was removed in backend.

      test case:

      • create any object
      • add one more location
      • open the second location in a frontend, non-legacy mode
      • reload, to check that Age: is increasing
      • in admin, remove second location
      • in frontend, keep reloading
      • object will be served until Age: >= s-maxage

        Issue Links

          Activity

          Hide
          Paulo Bras (Inactive) added a comment -

          note: after patch for issue EZP-22447, on removing an object or a location in admin, it appears that only the main location always triggers a purge.

          Show
          Paulo Bras (Inactive) added a comment - note: after patch for issue EZP-22447 , on removing an object or a location in admin, it appears that only the main location always triggers a purge.
          Show
          Jérôme Vieilledent (Inactive) added a comment - PR: https://github.com/ezsystems/ezpublish-legacy/pull/931
          Show
          Jérôme Vieilledent (Inactive) added a comment - Fixed in master: https://github.com/ezsystems/ezpublish-legacy/commit/c5ba7c06f77bd47f9a765439ce3f63a0cca1ca73
          Hide
          Eduardo Fernandes (Inactive) added a comment -

          QA Approved

          Show
          Eduardo Fernandes (Inactive) added a comment - QA Approved

            People

            • Assignee:
              Unassigned
              Reporter:
              Paulo Bras (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Due:
                Created:
                Updated:
                Resolved: