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

Make REST HTTP cache aware with Location ID expiry

    Details

    • Epic Link:
    • Sprint:
      Ventoux Sprint 1, Ventoux Sprint 2, Ventoux Sprint 3

      Description

      The REST MVC controllers should be modified in order to send the correct cache headers so that reverse proxies can be transparently used, like it is done in eZ\Publish\Core\MVC\Symfony\Controller\Content\ViewController::buildResponse()

        Issue Links

          Activity

          Hide
          Marcos Loureiro (Inactive) added a comment -

          QA Approved

          Show
          Marcos Loureiro (Inactive) added a comment - QA Approved
          Hide
          Marcos Loureiro (Inactive) added a comment -

          Yes of course.
          It's done.

          Show
          Marcos Loureiro (Inactive) added a comment - Yes of course. It's done.
          Hide
          Bertrand Dunogier added a comment -

          No, it's not really "known". It is cached because there is a response. The issue is that there is a response, not that it is cached. We have the same issue on locations (EZP-22055). Can you edit the issue and say that /user/groups is affected as well ?

          Show
          Bertrand Dunogier added a comment - No, it's not really "known". It is cached because there is a response. The issue is that there is a response, not that it is cached. We have the same issue on locations ( EZP-22055 ). Can you edit the issue and say that /user/groups is affected as well ?
          Hide
          Marcos Loureiro (Inactive) added a comment - - edited

          Note:
          For requests with path (like /user/groups/<path>)
          it will have different cache for the same object if we put the "/1" or not, example:
          The next request will have different caches

          GET /user/groups/5/12
          GET /user/groups/1/5/12 
          

          Probably this is known and it's the expected behavior.

          Show
          Marcos Loureiro (Inactive) added a comment - - edited Note: For requests with path (like /user/groups/<path>) it will have different cache for the same object if we put the "/1" or not, example: The next request will have different caches GET /user/groups/5/12 GET /user/groups/1/5/12 Probably this is known and it's the expected behavior.
          Hide
          Bertrand Dunogier added a comment -

          No, it's a redirect. So far, we don't cache redirects.

          Show
          Bertrand Dunogier added a comment - No, it's a redirect. So far, we don't cache redirects.
          Hide
          Bertrand Dunogier added a comment -

          It is the expected behaviour. An unpublished version doesn't have a location, and this story is only about items that can be cached (and expired) based on a location id.

          Show
          Bertrand Dunogier added a comment - It is the expected behaviour. An unpublished version doesn't have a location, and this story is only about items that can be cached (and expired) based on a location id.
          Hide
          Bertrand Dunogier added a comment -

          Merged to master

          Show
          Bertrand Dunogier added a comment - Merged to master
          Hide
          Bertrand Dunogier added a comment -

          Pull-request: ezpublish-kernel-659.

          Show
          Bertrand Dunogier added a comment - Pull-request: ezpublish-kernel-659 .

            People

            • Assignee:
              Unassigned
              Reporter:
              Bertrand Dunogier
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 3 days Original Estimate - 3 days
                3d
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 4 days, 5 hours, 30 minutes
                4d 5h 30m

                  Agile