Table 1 Client HTTP Headers Supported by the HP 3PAR WSAPI for Requests (continued)
RequiredValuesDescriptionHeader
Yes, for requests
with a message
body.
application/jsonThe format of the body.Content-Type
Yes, except for a
request to create
credentials.
The result of a credentials creation
request.
A key associated with the
user that created
credentials.
X-HP3PAR-WSAPI-SessionKey
Client HTTP Header Examples
When querying the CPGs, the client sends the following:
GET /api/v1/cpgs HTTP/1.1
Accept: application/json
Accept-Language: en
X-HP3PAR-WSAPI-SessionKey: 1-c86aedb2e7e98b4119cd74b624b8576b-b06d2d50
When creating a CPG, the client sends the following:
POST /api/v1/cpgs HTTP/1.1
X-HP3PAR-WSAPI-SessionKey: 1-c86aedb2e7e98b4119cd74b624b8576b-b06d2d50
Accept: application/json
Content-Type: application/json
Content-Length: 27
{
"name" : "t887-cpg"
}
Server HTTP Headers
Table 2 (page 13) shows HTTP headers included by the Web Services API in responses.
Table 2 Server HTTP Headers in the WSAPI
DescriptionValueHTTP Header
The HP 3PAR Web Services API Server.HP3PAR-WSAPIServer
Disables caching by mechanisms between the Web Services
API server software and client (HTTP RFC 2616), for HTTP/1.0
and 1.1.
no-cacheCache-Control
Disables caching by mechanisms between the Web Services
API server software and client (HTTP RFC 2616), for HTTP/1.0
and 1.1.
no-cachePragma
Indicates that the connection will be closed after completion
of the response (HTTP RFC 2616).
closeConnection
Included when the message body, which will be in JSON
format, is nonempty.
application/jsonContent-Type
The path portion of the URI of a newly created or updated
object, such as:
Varies. See the example in
the Description column.
Location
/api/v1/volumes/foo
Encoding is UTF-8 and percent encoded per RFC 3986.
The date and time at which the message was originated, per
RFC 2616.
Varies according to the
date.
Date
Overview 13