Provide a way for a client to discover the configuration used to resolve a request

XMLWordPrintable

    • Hide

      The following approach was suggested, and briefly included in the draft, but then removed:

      Where the response to a GET is a single versioned resource, the server SHOULD include a <code>Configuration-Context</code> header indicating the precise configuration in which that resource was found.
      Note this is frequently not the same as the context on the request: the context on the request is likely to be a global configuration, while the context on the response, if present, MUST be the leaf-level provider-specific configuration contributed to the requested context.

      Show
      The following approach was suggested, and briefly included in the draft, but then removed: Where the response to a GET is a single versioned resource, the server SHOULD include a <code>Configuration-Context</code> header indicating the precise configuration in which that resource was found. Note this is frequently not the same as the context on the request: the context on the request is likely to be a global configuration, while the context on the response, if present, MUST be the leaf-level provider-specific configuration contributed to the requested context.
    • Hide

      Defer from consideration in 1.0

      Show
      Defer from consideration in 1.0

      The spec allows a client to provide a configuration context using either a header or a query string, but there is no way for the client to discover if this configuration was actually used, or which contribution to a global configuration was used, to satisfy the request.

            Assignee:
            Unassigned
            Reporter:
            Nick Crossley (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: