[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OSLCCORE-164) OSLC paging should support POST with an application/x-www-form-urlencoded body
[ https://issues.oasis-open.org/browse/OSLCCORE-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Honey updated OSLCCORE-164: --------------------------------- Description: https://issues.oasis-open.org/browse/OSLCCORE-124 describes a proposal that POST with application/x-www-form-urlencoded body should be supported to avoid hitting URI length limits. OSLC paging described in http://open-services.net/bin/view/Main/OslcCoreSpecification#Resource_Paging describes how an oslc:ResponseInfo should include an oslc:nextPage link and that a client fetches the next page with a GET. However, requests, especially those for query, are likely to contain query parameters with long values such that URI length limits are broken. For paged query results, getting a page of results is more likely to exceed URI length limits as a stateless implementation will have to include additional parameter(s). (was: https://issues.oasis-open.org/browse/OSLCCORE-124 describes a proposal that POST with application/x-www-form-urlencoded body should be supported to avoid hitting URI length limits. OSLC paging described in http://open-services.net/bin/view/Main/OslcCoreSpecification#Resource_Paging describes how an oslc:ResponseInfo should include an oslc:nextPage link and that a client fetches the next page with a GET. However, requests, especially those for query, are likely to contain query parameters with long values such that URI length limits are broken. However, for paged query results, getting a page of results is more likely to exceed URI length limits as a stateless implementation will have to include additional parameter(s).) > OSLC paging should support POST with an application/x-www-form-urlencoded body > ------------------------------------------------------------------------------- > > Key: OSLCCORE-164 > URL: https://issues.oasis-open.org/browse/OSLCCORE-164 > Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC > Issue Type: Improvement > Components: Core > Reporter: David Honey > Assignee: James Amsden > > https://issues.oasis-open.org/browse/OSLCCORE-124 describes a proposal that POST with application/x-www-form-urlencoded body should be supported to avoid hitting URI length limits. OSLC paging described in http://open-services.net/bin/view/Main/OslcCoreSpecification#Resource_Paging describes how an oslc:ResponseInfo should include an oslc:nextPage link and that a client fetches the next page with a GET. However, requests, especially those for query, are likely to contain query parameters with long values such that URI length limits are broken. For paged query results, getting a page of results is more likely to exceed URI length limits as a stateless implementation will have to include additional parameter(s). -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]