OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (OSLCCORE-184) oslc:postBody does not indicate it should be used only for OSLC paging

Nick Crossley created OSLCCORE-184:

             Summary: oslc:postBody does not indicate it should be used only for OSLC paging
                 Key: OSLCCORE-184
                 URL: https://issues.oasis-open.org/browse/OSLCCORE-184
             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
          Issue Type: Improvement
          Components: Core, Query
            Reporter: Nick Crossley
            Assignee: James Amsden

oslc:postBody, in its shape and vocabulary entries, says that this property defines the body of a POST request to return the next page if the response was to a POST request, going on:

"Where a paged resource supports POST with an application/x-www-form-urlencoded body as an alternative to GET toÂavoid the request URI exceeding server limitations, the oslc:ResponseInfo in the response to the POST SHOULDÂcontain this property so that a client knows what to POST to get the next page."

This may be applicable to OSLC 2.0 paging, but it is incompatible with LDP paging. LDP paging uses 303 redirects, which should be followed using a GET request. The http spec states:
 The 303 (See Other) status code indicates that the server is
 redirecting the user agent to a different resource, as indicated by a
 URI in the Location header field, which is intended to provide an
 indirect response to the original request. A user agent can perform
 a retrieval request targeting that URI (a GET or HEAD request if
 using HTTP), which might also be redirected, and present the eventual
 result as an answer to the original request. Note that the new URI
 in the Location header field is not considered equivalent to the
 effective request URI.

This status code is applicable to any HTTP method. It is primarily
 used to allow the output of a POST action to redirect the user agent
 to a selected resource, since doing so provides the information
 corresponding to the POST response in a form that can be separately
 identified, bookmarked, and cached, independent of the original

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]