HTTP Message Forwarder Message Flow
The sender of a message packages and sends the data as an HTTP POST request, which sends the request to a URL configured on the HTTP server for the HTTP Message Forwarder. The HTTP server receives the request and forwards it to the HTTP Message Forwarder, which takes the incoming message and forwards it to the message destination via an HTTP POST request.
Then, the HTTP Message Forwarder keeps the incoming HTTP connection open until the message destination returns with the appropriate HTTP status code. This status code and any response data is then returned to the sender via the open HTTP connection with any data that the destination provides. If the HTTP Message Forwarder is unable to forward the incoming message to the message destination, the appropriate HTTP status code indicating this error is returned to the sender. Once the status code and the response data, if any, is returned to the sender, the HTTP connection for the incoming message will be closed.
This table describes the inbound flow of messages through the HTTP Message Forwarder.
| Stage | Process |
|---|---|
| 1 | The incoming message is sent to the HTTP server
via an HTTP or HTTPS POST request, using the SCHTTPMessageForwarder.dll file.
An example URL is: |
| 2 | Microsoft IIS routes the request to the HTTP Message Forwarder. |
| 3 | The HTTP Message Forwarder parses the URL and looks for a routing parameter. If one is found and configured, the POST is forwarded to the destination URL that is configured for that routing parameter. If the routing parameter is not found, the default destination URL is used. If the routing parameter is not configured, the incoming POST is discarded. All forwarding is performed via an HTTP POST or an HTTPS POST. |
| 4 | This HTTP status code is sent to the sender of the incoming message. |