[OASIS Issue Tracker] (OSLCCORE-124) Query spec doesn't say whether POST with application/x-www-form-urlencoded should be supported

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

David Honey created OSLCCORE-124:
------------------------------------

             Summary: Query spec doesn't say whether POST with application/x-www-form-urlencoded should be supported
                 Key: OSLCCORE-124
                 URL: https://issues.oasis-open.org/browse/OSLCCORE-124
             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
          Issue Type: Improvement
          Components: Query
            Reporter: David Honey
            Assignee: James Amsden


The spec only mentions use of GET. However, the obsolete document at https://open-services.net/bin/view/Main/OslcSimpleQuerySemanticsV1 it references says:

"However, if the query parameters are very long, it may be preferable to instead request the result of the query by sending an HTTP POST request to the base URL and include the query parameters in the HTTP request body as content with media type application/x-www-form-urlencoded. In REST parlance, this is sometimes refered to as an overloaded POST. In the following sections we'll normally talk about appending query parameters to the base URL to form a query URL, and sending an HTTP GET request to the query URL with the understanding that similar statements apply to the HTTP POST case."

It's not clear whether the POST alternative for query is meant to be part of the spec or not.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)