HCP System Management Help
The HEAD request to check the existence of an object or multiple version has these elements:
•If you’re accessing the namespace as an authenticated user, an Authorization header
•The URL of the object or symbolic link
By default, the HEAD request to check the existence of object versions does not include deleted versions (that is, the marker versions that indicate when an object was deleted). To include deleted versions, specify this URL query parameter:
deleted=true
You can also specify deleted=false, which results in the default behavior.
Checking the existence of a specific old version
To check the existence of a specific old version of an object, specify the version URL query parameter with the ID of the version you want. You can omit this parameter to check the existence of the current version of an object.
To find the ID of the version you want, list the versions of the object. For more information on listing the versions of an object, see Listing object versions.
Checking the existence of the latest version at a specified time
To check the existence of the latest version of an object at a specified time, specify the version URL query parameter with the ingest time of the version you want. You can omit this parameter to check the existence of the current version of an object.
To find the ingest time of the version you want, list the versions of the object. For more information on listing the versions of an object, see Listing object versions.
Checking the existence of a range of versions
To check the existence of a range of versions of an object, specify the version URL query parameter with the range of object version IDs you want. You can omit this parameter to check the existence of the current version of an object.
To find the ID of the versions you want, by list the versions of the object, as described in Listing object versions.
The version range query parameter has this format:
?version=<StartVersionID>-<EndVersionID>
The table below shows the ways in which you can specify the range.
Range specification | Description | Example |
---|---|---|
StartVersionID–End-VersionID |
VersionID in StartVersionID through EndVersionID, inclusive. |
Object versions beginning with 91728994268353 through object version 91728994618369: 91728994268353-91728994618369 |
StartVersionID- |
VersionID in StartVersionID through the end of the object versions. |
All the bytes beginning with 91728994618369 and continuing through the end of the object versions: 91728994618369- |
0- | All VersionIDs. | All object versions: 0- |
These rules apply to the version range query parameter:
•If you omit the parameter, HCP checks the existence of the current version of an object.
•If you specify a valid range, HCP returns the requested amount of data with a status code of 200.
Conditionally checking the existence of a single object or version
To check the existence of a single object or version only if the object meets certain conditions, use one of the headers listed in Conditional operations.
Checking the existence of a specific version
To check for the existence of a specific version of an object, specify the version URL query parameter with the ID of the version you want.
Trademarks and Legal Disclaimer
© 2017 Hitachi Vantara Corporation. All rights reserved.