Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-12176

Provide information about changes in the Proxy Config API between calls

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • System
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started

      Add information about the configuration returned by the /admin/api/account/proxy_configs/ENVIRONMENT.json - either the last time it was changed, or some kind of hash that would identify the current state (e.g. the latest configuration versions of al services).

      The purpose is to prevent APIcast from re-downloading and reapplying the configuration, if there were no changes since the last time the configuration was fetched - it might be an expensive operation, if many services are configured, and skipping this step would be useful.

      We can consider returning a 304 status code (see https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/304) and use If-Modified-Since header, or adding this metadata in the response body or some other response header.

      We need to make sure though that the information about the deleted service gets propagated successfully, i.e. a service is deleted between configuration fetches, APIcast needs to get the updated configuration and reconfigure the services.

              Unassigned Unassigned
              rhn-support-dmayorov Daria Mayorova
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: