Simple HTTP Node
 | Simple HTTP Node | Sends HTTP requests to a given URI and returns the provided response. |
The Simple HTTP Node asynchronously sends requests to a given target, waits for a response and then returns it in its outputs.
Inputs
The Method determines which kind of HTTP message you want to send. There are GET, DELETE, POST, HEAD and PUT methods available currently. The URL determines the target of the HTTP request. If no protocol is provided in the URL it automatically uses HTTP (as opposed to HTTPS). The Request Body property provides a string that the HTTP request will use as the content's body.
The Request Header Names and Request Header Values arrays give the request a list of headers. Each value is assigned to the header name at the same position in the respective array. If a header name appears multiple times, they are assigned every corresponding value like expected. If a header from these lists is illicit on the request, the HTTP Node will try to add it to the content's headers instead.
If Ventuz sends the same request (using the same Method, URL, Request Body and Headers) in the same frame multiple times, it will collect the requests and instead only send one of them, providing the response to all sending HTTP Nodes. You can turn this behavior off by enabling the Force Send property. This option becomes useful e.g. when you need to reliably POST objects on an HTTP server.
Outputs
The Response Body contains the response's body as a String. It is also provided as a Byte Array in the Response Body Bytes property. The headers of the response are provided in the Response Header Name and Response Header Values properties in the same way as described in the Inputs. The Status Code and Message properties reflect the response's status. These are status codes and messages defined in the HTTP specificiation. On Receive and On Failed are fired according to the response's status.
Limitations
Currently the HTTP node has some limitations:
- Ventuz does not handle Cookies, so you might need to manually handle e.g. sessions or authentication or use appropriate methods
- Redirects are not handled automatically, you need to manually re-send the HTTP Message to the returned URI.