HTTP client
Description
The HTTP client transform performs a simple call to a base URL with options appended as shown below:
http://<URL>?param1=value1¶m2=value2¶m3..
The result is stored in a String field with the specified name.
Options
Option | Description |
---|---|
Transform name | Name of the transform; this name has to be unique in a single pipeline |
URL | The base URL string |
Accept URL from field? | Enable this option if you want to get the URL from a previous transform. Enabling this will also allow you to specify the name of the input field. |
URL field name | The name of the incoming field that contains the URL |
Connection timeout | |
Socket timeout | The number of seconds to wait if no data is returned from the server. |
Connection close wait time | Result fieldname |
The name of the field to store results | HTTP status code field name |
The name of the field to store the HTTP response code (e.g. 200, 404) | Response time (milliseconds) field name |
The name of the field to store the response time | Http Login |
The username to be passed during HTTP (Basic) authentication | HTTP Password |
The password to be passed during HTTP (Basic) authentication | Proxy Host |
The hostname of the Proxy Server to be used | Proxy Port |
The port number of the Proxy Server to be used | Parameters |
Area where you define the parameter name-value pairs to pass on the URL | Custom HTTP Headers |
FAQ
The HTTP client transform doesn’t do anything
Q: The HTTP client transform doesn’t do anything, how do I make it work?
A: The HTTP client transform needs to be triggered. Use a Row generator transform generating e.g. 1 empty row and link that with a hop to the HTTP client transform.
The HTTP client transform and SOAP
Q: Does the HTTP client support SOAP?
A: No, it just calls an URL with arguments. Future transforms may provide SOAP functionality, Work is underway on a WebService transform supporting WSDL.