Protocol And Message Format; Client Http Headers; Client Http Headers Supported By The Hp 3Par Wsapi For Requests - HP 3PAR StoreServ 7200 2-node Manual

Hp 3par web service api 1.2 developer's guide (qr482-96192, june 2013)
Hide thumbs Also See for 3PAR StoreServ 7200 2-node:
Table of Contents

Advertisement

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- 1 6
UTF-32
UTF- 1 6BE
UTF-32BE
UTF- 1 6LE
UTF-32LE

Client HTTP Headers

The HTTP requests that clients make to the API server include HTTP headers.
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
Accept-Language
Content-Length
12
Accessing the WSAPI
Description
The response format the
client can accept.
The response language the
client can accept.
The length of the content in
bytes.
Values
One of the following:
application/json
application/*
application/json*
application/<anything>+json
*/json
*/*
*/json*
*/<anything>+json
where * is literally an asterisk (*)
and <anything> is any string of
characters.
One of the following:
*
en
en*
Number of bytes
Table 1 (page 12)
Required
No
No
Yes, for requests
with a message
body.

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents