Ballot Details: Issue 124 - Recommend server supports POST to query base URI (CLOSED)
|Ballot Question||Are you in favor of the proposal?|
|Ballot 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.
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.
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.
VOTING CLOSED: Tuesday, 23 January 2018 @ 3:00 pm EST
|Open Date||Tuesday, 16 January 2018 @ 3:00 pm EST|
|Close Date||Tuesday, 23 January 2018 @ 3:00 pm EST|
|Ballot Type||Official, as defined by organization policies and procedures|
|Number of votes cast (excluding abstentions)||5|
|Eligible members who have voted||5 of 8||62.5%|
|Eligible members who have not voted||3 of 8||37.5%|
|Options with highest number of votes are bold|
|Option||# Votes||% of Total|