[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [EXT] Re: [cti] TAXII 2.1 WD 09 reminder
Thanks, Bret for clarifying on Slack; I retract the below. I was obviously unclear on taxii 2.1 dropping the range headers completely. From: Bret Jordan <Bret_Jordan@symantec.com> Matt, The Range headers were completely dropped from 2.1, that was done way back in Working Draft 01. Bret From: Matt Pladna <mpladna@lookingglasscyber.com> Bret, Thanks for the reminder. I reviewed the pagination text in WD 09. I donât believe itâs clear enough about the two pagination methods being allowed: Range/Content-Range headers from 2.0 and Limit Parameter in 2.1. I took a stab at drafting
up some text below. Note that my headers are probably not sized right for be sub sections. Iâd appreciate you and a couple others reviewing and weighing in. Iâve modified slightly the main pagination section and added subsections to clearly split the range pagination from limit param. 3.5 Pagination
TAXII 2.1 supports pagination of large result sets on certain endpoints. These endpoints return results sorted in ascending order by the date they were added to the collection (see
section 3.3).
The server may limit the number of responses in response to a query in one of two ways:
If more objects are available after a paginated response, either because the client requested that they be limited via the
limit parameter or the client/server limits them via
Range and
Content-Range headers, then the response
envelope
MUST have a value of true in the
more property and
MAY have an appropriate value in the next property. If the
more property is set to
true and the
next property is populated then the client can paginate through the remaining records using the
next URL parameter along with the same original query options. If the
more property is set to
true and the
next property is empty then the client may paginate through the remaining records by
It is possible for the server to return
"more": true in a response, yet present no additional objects in the follow-on query.
This can occur when the additional objects are deleted from a collection between requests. 3.5.1 Range/Content-Range Pagination
The
items range unit is defined for expressing subranges of a resource [HTTP
7233]. For the Endpoints that return
object,
items represents objects. For the Endpoints that return
collections,
items represents Collections. The first
items value in the
Range and
Content-Range headers gives the first item in a range. The last
items value in the
Range and
Content-Range headers gives the last item in the range; that is,
items ranges specified are inclusive.
items are zero-indexed; that is, the first item is object zero. A
Content-Range header will have a third value that identifies the size of the available
dataset. For example:
All
items values
MUST be:
â3.5.1.1â Range/Content-Range Requirements
The following requirements only apply to
items based range requests
NOTE: The total number of items available in a result may change with each request for a new page in the paginated result set. This can happen if items have been added or deleted between
subsequent requests. 3.5.2 Limit Parameter Pagination
From:
<cti@lists.oasis-open.org> on behalf of Bret Jordan <Bret_Jordan@symantec.com> All, Just a reminder that all comments and suggestions for TAXII 2.1 WD09 are due today. Thanks Bret |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]