Section 4.17: support new HTTP QUERY method, deprecate /$query path suffix

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major
    • V4.02
    • Affects Version/s: V4.01_OS
    • Component/s: URL Conventions
    • None
    • Hide

      Rephrase section 4.17 to use the new QUERY method with a request body of Content-Type: application/x-www-form-urlencoded or application/json as defined by ODATA-1405.

      Require all query options to be passed in the request body (rationale: mixed locations for query options are an unnecessary complication).

      Deprecate the current approach using POST and path suffix /$query.

      Show
      Rephrase section 4.17 to use the new QUERY method with a request body of Content-Type: application/x-www-form-urlencoded or application/json as defined by ODATA-1405 . Require all query options to be passed in the request body (rationale: mixed locations for query options are an unnecessary complication). Deprecate the current approach using POST and path suffix /$query .

      The IETF Draft The HTTP QUERY Method defines a new HTTP method QUERY that basically is a "GET with request body", being

      • safe
      • idempotent
      • cacheable, with the request body incorporated in the cache key

      This could replace the OData-specific solution POST .../$query defined in section 4.17 Passing Query Options in the Request Body.

            Assignee:
            handl
            Reporter:
            handl
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: