Response Headers
The following section describes the required and optional response headers. The response headers are applicable to HTTP methods (PUT, GET, POST and DELETE).
Response Headers
The following HTTP response headers are always provided in the response to all requests.
| HTTP Header | Description |
|---|---|
| Date | The date and time, from the perspective of the management console clock, at which the response message was generated. As required by the HTTP protocol specification, this date is an HTTP full date sent in the RFC 1123-defined fixed length format. Example: Sun, 08 Oct 1961 10:08:00 GMT |
| X-Transaction-ID | Returns the same X-Transaction-ID set by the client. If it is set by the client, server auto-generated alpha numeric value is returned. |
Optional Response Headers
The following HTTP response headers are provided in response to all requests except those that result in a 204 (No Content) HTTP status code.
| HTTP Header | Description |
|---|---|
| Content-Length | When used in a response, specifies the length of the response body. If omitted, the response does not contain a body. |
| X-HMC-Schema-Version | Specifies the schema version. When specified with an HMC version 1.1.0 against an HMC version 1.2.0, response contains attributes introduced till version 1.1.0. If the schema version is not specified, the latest version supported by HMC is returned as response. |
| ETag | Used to assist in caching of the response by the client. Holds an opaque identifier or checksum of the returned element. |
| Last-Modified | Used to assist in caching of the response by the client. Holds an opaque timestamp of the returned element. Granularity of the time stamp is one second. |
| Location | Returned on PUT. Holds the URL of the newly created element. |
