REST Error Handling
Each response to a request to RS Gateway produces an HTTP result code. This result
code indicates the success or failure of the request being received for processing.
Additionally, each successfully processed request generates a response and all responses contain
a Result
(numeric code) field and ResultText
(string) field
that describe whether the engine was able to perform the request.
HTTP Response Codes lists the out-of-the-box mapping of HTTP response codes to RS Gateway result codes.
HTTP Response Code | Name | RS Gateway Code and Description |
---|---|---|
200 | OK |
|
400 | Bad Request |
|
401 | Unauthorized |
|
404 | Not Found |
|
409 | Conflict |
|
422 | Unprocessable Entity | MATRIXX Engine understands the content type of the request entity, but was unable to process the contained
instructions. For example, this error condition may occur if an XML request body contains well-formed (syntactically correct), but semantically erroneous, XML instructions.
|
500 | Internal Server Error |
|
If a POST request results in an error, the response includes a _resultCode
that corresponds to the actual error and the _resultText
includes a
description of the error.
For information about MATRIXX Engine result codes, see the discussion about engine validation error codes in MATRIXX Administration. For information about SubMan API result codes, see the discussion about SubMan API result codes. For information about changing the out-of-the-box mapping, see the discussion about mapping error codes to HTTP result codes.