HCP System Management Help
Some response headers are common to all HSwift requests. The table below describes those headers. Response headers that are specific to certain requests are described in the sections for those requests in Working with containers and Working with objects.
Name | Description |
---|---|
Content-Length |
The size, in bytes, of the response body if HCP can determine the size before formulating the response. If the response does not include a response body, the value of the Content-Length is 0 (zero). |
Content-Type |
The Internet media type of the response body if HCP can determine the Internet media type. If HCP cannot determine the Internet media type, the value of this header is application/octet-stream. Because HCP returns error information in a response body, the response to any request can include a Content-Type header. |
Date |
The date and time at which HCP responded to the request in Greenwich Mean Time (GMT). The date and time are returned in this format: DDD dd MMM yyyy HH:mm:ss GMT For example: Thu, 14 Mat 2013 14:27:05 GMT |
Server | The system that responded to the request. The value of this header is always HCP followed by the HCP version number (for example, HCP V7.1.0.16) |
Transfer-Encoding |
Always chunked. This header is returned if the response includes a response body but HCP cannot determine the size of the response body before formulating the response. Because HCP returns error information in a response body, the response to any request can include a Transfer-Encoding header. |
X-Trans-Id | HCP returns a universally unique identifier (UUID). This UUID does not map to any entries in the HCP database. |
Trademarks and Legal Disclaimer
© 2017 Hitachi Vantara Corporation. All rights reserved.