2020.1

Table Of Contents
l
Loop each attachment as a data file: When receiving attachments through a POST
request (HTML Form), this option will make the HTTP Server Input task loop through
each attachment. Each data file is an XML with the accompanied file.
l
Do not include XML envelope: Only active when the previous Loop option is
checked. When checked, the XML file containing the request data will not be
available. Only the attachment itself is sent as a data file.
l
Respond on error: Enter a message to be sent to the client as the output file if the
process encounters an error and is unable to send a reply that includes the actual output
file. The information can be in any desired format such as HTML or plain text. However, if
it must be displayed in a browser, the format should match the selected MIME type.
This is a variable property box. You can use any combination of text, variables and data
selections; see "Variable task properties" on page301.
Note
This option requires every plugin in the process to be explicitly set to "On Error:
Stop process" (see ), even if the process itself is set to "On Error: Stop process".
l
Send immediate response to client: Do not wait for the process to finish and send a
static HTML or Text file back to the client instead. This prevents any timeout from
occurring. When checking this option, the field under the option is used to select which
file to return.
l
Use custom HTTP server response code: When the process ends and a response is
sent to the requesting client, a custom response code can be specified depending on how
the process goes. While in previous versions the "200 OK" code was always used, this
option overrides it to, for example, "404 Not Found" or "401 Unauthorized".
Note
The response code must start with 3 digits, followed by a space and then the error
message. If the first few characters can't be converted to a valid number, the server
automatically returns "500 Internal Server Error", regardless of the actual response
code provided by the process.
Page 331