The table below describes the request-specific response headers for this operation. For information on all HCP-specific response headers, see HCP-specific HTTP response headers.
Header | Description |
---|---|
Content-Type |
Always text/xml. |
Content-Length |
The size of the annotation, in bytes. |
ETag |
The ETag of the object or version enclosed in double quotation marks ("). |
X-HCP- ChangeTimeMilliseconds |
The change time for the annotation, in milliseconds since January 1, 1970, at 00:00:00 UTC, followed by an integer that’s unique for the change time (for example, 1336483100178.00). For information on object change times, see Object ingest time and change time. |
X-HCP-ChangeTimeString |
The change time for the annotation in this format: yyyy-MM-ddThh:mm:ssZ In this format, Z represents the offset from UTC and is specified as: (+|-)hhmm For example, 2012-05-08T09:18:20-0400 represents the start of the 20th second into 9:18 AM, May 8, 2012, EDT. |
X-HCP-Hash |
The cryptographic hash algorithm HCP uses, along with the cryptographic hash value stored for the annotation, in this format: X-HCP-Hash: hash-algorithmhash-value You can use the returned hash value to verify that the stored annotation is the same as the annotation you originally sent. To do this, compare this value with a hash value that you generate from the original data. |
X-HCP-Size |
The size of the annotation, in bytes. |
X-HCP-SymlinkTarget |
The path to the target object as specified when the symbolic link was created. This header is returned only if the URL specifies a symbolic link. If this header is returned, the X-HCP-ACL value is always false. |
X-HCP-Type |
Always annotation. |
If HCP does not find the specified annotation, it returns an X-HCP-ErrorMessage header with the message “No annotation exists with name annotation-name.”
© 2017 Hitachi Data Systems Corporation. All rights reserved.