HCP Tenant Management Help


Request contents (GET object versions)

The GET request to list object versions has these elements:

If you’re accessing the namespace as an authenticated user, an Authorization header.

The URL of the object.

A version=list URL query parameter.

If you specify a condition, the HCP returns a version list only if all versions of the object meet the specified condition.

By default, a list of object versions does not include delete markers. To retrieve a listing that includes delete markers, specify this URL query parameter:

deleted=true

You can also specify deleted=false, which results in the default behavior.

Listing a range of versions using version IDs

To list a range of versions of an object, specify the version URL query parameter with the range of object version IDs you want to list.

To find the ID of the versions you want, by list the versions of the object, as described in Listing object versions.

The version query parameter has this format:

?version=<StartVersionID>-<EndVersionID>

The table below shows the way in which you can specify the range.

Range specification Description Example

StartVersionIDEnd-VersionID

VersionID in StartVersionID through EndVersionID, inclusive.

Object versions beginning with 91728994268353 through object version 91728994618369: 91728994268354-91728994618369

These rules apply to the version query parameter:

If you omit the parameter, HCP lists the current version of an object.

If you specify a valid range, HCP lists the requested amount of data with a status code of 200.

Listing a range of versions using timestamps

To list a range of versions of an object using the version create time timestamps, specify the version URL query parameter with the range of object timestamps you want.

To find the version create times of the versions you want, by listing the timestamps of the versions, see Listing object versions.

The version query parameter with create timestamp range has this format:

?version=@start-Create-Time-Milliseconds-@end-Create-Time-Milliseconds

The table below shows the way in which you can specify the range.

Range specification Description Example

@start-Version-Create-Time-Milliseconds
@end-Version-Create-Time-Milliseconds

Version timestamp in start-Version-Create-Time-Milliseconds, exclusive, through end-Version-Create-Time-Milliseconds, inclusive

Object versions beginning at version create timestamp 1493911519817 through version create timestamp 1493911519820: @1493911519817–@1493911519820

These rules apply to the version ingest timestamp range query parameter:

If you omit the parameter, HCP lists the current version of an object.

If you specify a valid range, HCP lists the requested amount of data with a status code of 200.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.