HP 3PAR StoreServ 7400 4-node HP 3PAR Web Service API 1.2 Developer's - Page 12
Protocol and Message Format, Client HTTP Headers
View all HP 3PAR StoreServ 7400 4-node manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 12 highlights
Protocol and Message Format Clients communicate with the WSAPI server using HTTPS and data structures represented with JSON. The supported JSON character encodings include the following formats: • ASCII • ISO-8859-1 • US-ASCII • UTF-8 • UTF-16 • UTF-32 • UTF-16BE • UTF-32BE • UTF-16LE • UTF-32LE Client HTTP Headers The HTTP requests that clients make to the API server include HTTP headers. Table 1 (page 12) shows the required and optional HTTP headers. Optional headers, when present, must be one of the values listed in the Values column. For example: Accept: application/json; charset=UTF-8 Table 1 Client HTTP Headers Supported by the HP 3PAR WSAPI for Requests Header Accept Description The response format the client can accept. Values Required One of the following: No • application/json • application/* • application/json* • application/+json • */json • */* • */json* • */+json where * is literally an asterisk (*) and is any string of characters. Accept-Language Content-Length The response language the One of the following: client can accept. •* • en • en* The length of the content in Number of bytes bytes. No Yes, for requests with a message body. 12 Accessing the WSAPI