The table below describes the HTTP return codes that have specific meaning for this request. For descriptions of all possible return codes, see HTTP return codes.
Code | Meaning | Description |
---|---|---|
200 |
OK |
HCP found the specified object or version and returned its metadata. This code is also returned if the specified URL identifies a directory, not an object. |
204 |
No Content |
The requested version is a deleted version. |
304 |
Not Modified |
One of: •The request specified an If-None-Match header, and the ETag of the requested object or version matches the value in the header. •The request specified an If-Modified-Since header, and the object change time is at or before the time specified in the header. |
400 |
Bad Request |
The request was not valid. These are some, but not all, of the possible reasons: •The URL in the request is not well-formed. •The namespace does not exist. •The request included an If-Match or If-None-Match header and the object does not yet have an ETag. •The request contains an unsupported query parameter or an invalid value for a query parameter. If more information about the error is available, the HTTP response headers include the HCP-specific X‑HCP-ErrorMessage header. |
404 |
Not Found |
One of: •HCP could not find a directory, object, or version at the specified URL. The specified object or version does not exist, or the request specified the current version of an object that has been deleted. •Any component of the URL except for the last component in the path is a symbolic link to a directory. |
412 |
Precondition Failed |
One of: •The request specified an If-Match header, and the ETag of the requested object or version does not match the value in the header. •The request specified an If-Unmodified-Since header, and the object change time is after the time specified in the header. |
© 2015 Hitachi Data Systems Corporation. All rights reserved.