Looking for Iguana v.5 or v.6? Learn More or see the Help Center.
The Iguana HTTP Component Response Protocol |
The response to an HTTP request is a plain-text message which consists of the following information:
- A version string, followed by the carriage return and line feed characters;
- An error code, followed by a carriage return and line feed characters;
- Additional information if a failure occurred.
Here is an example of a successful response:
HTTP/1.1 200 OK Content-Length: 9 VERSION 1.0 SUCCEEDED |
Here is an example of a error response:
HTTP/1.1 200 OK Content-Length: 47 VERSION 1.0 CHANNEL_ERROR Channel 'testFromHttp' is not running. |
The following table lists all of the error codes that can be returned from the remote channel. If an error is listed as Fatal, the sending channel is stopped. Otherwise, the channel will continue to try to send the message until successful or until a fatal error occurs.
| Response Code | Fatal/Retry | Description |
|---|---|---|
| SUCCEEDED | N/A | The message was successfully processed. |
| GENERAL_ERROR | Retry | Some unhandled exception occurred on the remote channel. |
| CHANNEL_ERROR | Retry | The target channel is not running, or some other non-fatal error has occurred. |
| CHANNEL_ERROR_FATAL | Fatal | Occurs when the target channel does not exist, when the channel does not contain a From HTTPS component, or when some other channel-related fatal error has occurred. |
| INVALID_REQUEST | Retry | The request is missing required information or is in the wrong format. |
| MESSAGE_TRY_AGAIN | Retry | The channel is busy; try again later. |