HP 3PAR StoreServ 7200 2-node HP 3PAR Web Service API 1.2 Developer's - Page 19

Operation-specific status and error codes for the WSAPI are described in, Table 6

Page 19 highlights

Table 5 Generic WSAPI code Member Status and Error Codes (continued) API Error API Error Code HTTP Code Description ref member contains the name of the member. INV_HTTP_HEADER 62 400 Bad Request Invalid HTTP header syntax. INV_UTF 63 400 Bad Request A request body contains a sequence of characters that is invalid for the supported UTF encodings. INV_INPUT_NO_REQ 64 400 Bad Request A POST request is missing a JSON request body. INV_HTTP_REQ 65 400 Bad Request The request line (first line) of an HTTP request does not comply with the form specified for "Request-Line" in RFC 2616. INV_URI 66 400 Bad Request The URI is not absolute, contains characters not allowed in a URI, contains invalid percent encoding, or, after percent decoding, contains an invalid UTF-8 character sequence. INV_POST_ACTION 67 400 Bad Request An HTTP POST request contains an action member with an invalid value. SYS_SVC_NOT_READY 68 503 Service Services that the system Unavailable depends on in order to process the requested operation are not ready. INV_INPUT_ILLEGAL_CHAR 69 400 Bad Request Input contains one or more illegal characters. UNLICENSED_FEATURE 70 403 Forbidden System is not licensed for this feature or functionality. SYSTEM_ERR 95 500 Internal A system service on which Server Error the API server depends has returned an unexpected error, preventing the API server from fulfilling the request. (Since WSAPI 1.2) Operation-specific status and error codes for the WSAPI are described in Table 6 (page 20). HTTP Status and Error Codes 19

  • 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 5 Generic WSAPI
code
Member Status and Error Codes
(continued)
Description
HTTP Code
API Error Code
API Error
ref
member contains the
name of the member.
Invalid HTTP header
syntax.
400 Bad Request
62
INV_HTTP_HEADER
A request body contains
a sequence of characters
400 Bad Request
63
INV_UTF
that is invalid for the
supported UTF encodings.
A POST request is missing
a JSON request body.
400 Bad Request
64
INV_INPUT_NO_REQ
The request line (first line)
of an HTTP request does
400 Bad Request
65
INV_HTTP_REQ
not comply with the form
specified for
“Request-Line” in RFC
2616.
The URI is not absolute,
contains characters not
400 Bad Request
66
INV_URI
allowed in a URI, contains
invalid percent encoding,
or, after percent
decoding, contains an
invalid UTF-8 character
sequence.
An HTTP POST request
contains an action
400 Bad Request
67
INV_POST_ACTION
member with an invalid
value.
Services that the system
depends on in order to
503 Service
Unavailable
68
SYS_SVC_NOT_READY
process the requested
operation are not ready.
Input contains one or
more illegal characters.
400 Bad Request
69
INV_INPUT_ILLEGAL_CHAR
System is not licensed for
this feature or
functionality.
403 Forbidden
70
UNLICENSED_FEATURE
A system service on which
the API server depends
500 Internal
Server Error
95
SYSTEM_ERR
has returned an
unexpected error,
preventing the API server
from fulfilling the request.
(Since WSAPI 1.2)
Operation-specific status and error codes for the WSAPI are described in
Table 6 (page 20)
.
HTTP Status and Error Codes
19