Document:
03165: Issue 124 - Recommend server supports POST to query base URI

Draft (A preliminary unapproved sketch, outline, or version.)

Details

Submitted By Dr. Martin Sarabura on 2018-01-23 8:01 pm UTC

Publication Type

None at this time.

Group / Folder

OASIS OSLC Lifecycle Integration Core (OSLC Core) TC / System Ballot Results

Modified by

Not modified.

Copy

This document is not a copy.

Technical Contact

None at this time.

Download Count

457

Download Agreement

None at this time.

Description

Rationale for proposed change Many implementations have a limit on the maximum length of a URI string. The query specification does not describe how clients and servers should workaround such limits on a GET of a query base. Proposed change https://tools.oasis-open.org/version-control/browse/wsvn/oslc-core/trunk/specs/oslc-query.html Section 7, Using a Query Capability Change the first paragraph from: Executing a query or search is achieved by executing a GET on the query base URI of a query capability. To: Executing a query or search is achieved by executing a GET on the query base URI of a query capability. Servers SHOULD also support POST to the query base URI with content type application/x-www-form-urlencoded with a request body representing the query parameters. Many servers have a limit on the maximum length of a URI, and the POST usage is the standard mechanism to avoid the impact of such limits. Section 9, Query Result Paging has yet to be written. But it should also address this issue. Getting the first or next page using GET may hit the same limits. We can review that section when there is a proposed darft of it.