Dell Unity™ Family Unisphere® Management REST API Programmer's Guide

PDF

HTTP response headers

A response from the REST API always includes HTTP response headers that contain metadata about the response being sent. The following HTTP headers appear in every REST API response:

Table 1. HTTP response headers in the REST API
HTTP header	Description
Status Code	HTTP status code that indicates whether the request was successful.
Cache-Control	Specifies whether the response can be cached and/or stored in non-volatile storage. In this version of the REST API, the value is always no-cache, nostore, max-age=0, which indicates information should not be cached or stored.
Connection	Specifies the preferred type of connection. In this version of the REST API, the value is always Keep-Alive, which means the client/server connection is left open for the length of time specified in the Keep-Alive header.
Content-Language	Indicates the language of the response content. If the language specified in the request cannot be found, the language defaults to en-US (US English).
Content-Type	MIME type of the response. In this version of the REST API, the value is always application/json;version=4.0;charset=UTF-8.
Date	Date and time when the response was sent.
EMC-CSRF-TOKEN	Returned in the first GET request and required for subsequent POST and DELETE requests.
Expires	Date and time when the response information is considered to be expired.
Keep-Alive	The timeout parameter associated with the Keep-Alive header specifies the length of time for which the server will keep the client/server connection open between requests, in seconds. The max parameter specifies the number of requests allowed per connection. If set to 0, an unlimited number of requests are allowed.
Pragma	Implementation-specific directives. In this version of the REST API, the value is always no-cache, which indicates that the application should forward the request to the origin server, even if it has a cached copy of what was requested.
Server	REST API server name. In this version of the REST API, the value is always Apache.
Transfer-Encoding	Indicates how the response was transmitted. In this version of the REST API, the value is always chunked.

When you log into the REST API, the response also includes a Set-Cookie header, which contains information about the login session. The response can include other cookies as well. You must include these cookies in each request that uses this login session.