HP 3PAR StoreServ 7450 4-node HP 3PAR Web Service API 1.2 Developer's - Page 13

Server HTTP Headers, Table 1 Client HTTP Headers Supported by the HP 3PAR WSAPI for Requests

Page 13 highlights

Table 1 Client HTTP Headers Supported by the HP 3PAR WSAPI for Requests (continued) Header Description Values Required Content-Type The format of the body. application/json Yes, for requests with a message body. X-HP3PAR-WSAPI-SessionKey A key associated with the user that created credentials. The result of a credentials creation request. Yes, except for a request to create credentials. 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 HTTP Header Server Cache-Control Pragma Connection Content-Type Location Value Description HP3PAR-WSAPI The HP 3PAR Web Services API Server. no-cache Disables caching by mechanisms between the Web Services API server software and client (HTTP RFC 2616), for HTTP/1.0 and 1.1. no-cache Disables caching by mechanisms between the Web Services API server software and client (HTTP RFC 2616), for HTTP/1.0 and 1.1. close Indicates that the connection will be closed after completion of the response (HTTP RFC 2616). application/json Included when the message body, which will be in JSON format, is nonempty. Varies. See the example in the Description column. The path portion of the URI of a newly created or updated object, such as: /api/v1/volumes/foo Encoding is UTF-8 and percent encoded per RFC 3986. Date Varies according to the date. The date and time at which the message was originated, per RFC 2616. Overview 13

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107

Table 1 Client HTTP Headers Supported by the HP 3PAR WSAPI for Requests
(continued)
Required
Values
Description
Header
Yes, for requests
with a message
body.
application/json
The 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
Description
Value
HTTP Header
The HP 3PAR Web Services API Server.
HP3PAR-WSAPI
Server
Disables caching by mechanisms between the Web Services
API server software and client (HTTP RFC 2616), for HTTP/1.0
and 1.1.
no-cache
Cache-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-cache
Pragma
Indicates that the connection will be closed after completion
of the response (HTTP RFC 2616).
close
Connection
Included when the message body, which will be in JSON
format, is nonempty.
application/json
Content-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