...
Options | Description |
|---|---|
Step name | Name of the step; This name has to be unique in a single transformation |
URL | A static destination for the post request. |
Accept URL from field? | Enable this alternative in order to dynamically specify the post URL from a field. |
URL field name | Specify which field contains the URL post address (assuming that "Accept URL from field?" is checked.) |
Encoding | Specify the encoding of the post request |
Request entity field | The name of the field that will contain the post request. When enabled, the "Post a file" option will retrieve a file named in the Request entity field, and post the contents of that file. |
Post a file | Enable this in conjunction with "Request entity field" in order to send contents of a file as a post request. |
Result fieldname | Specify the fieldname to contain the result retrieved from the post request (optional). |
HTTP status code fieldname | Specify the fieldname to contain the HTTP status code (optional). [since version 3.2.3] |
Body (Header) Parameters | Specify multiple post parameters of the form Parameter=Name. Specific fields will fill the name part. Since version 3.2.3 you can specifiy if a specific parameter is put in the body (default=N) or header (Y). |
Query Parameters | Specify multiple query parameters of the form Value=Name. Specific fields will fill the name part. |
Note: The data of the input fields can be escaped by the Calculator step and the function "Mask XML content from string A" or "Escape HTML content"
Comments
Currently "Request entity field" must be filled in order for "Post a file" to work. Selecting "Post a file" and specifying a field under "Body parameters" without selecting a value for "Request entity field" (the place for the file name) will fail silently.