2020.2

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.
l
Response file: Select which file to return. Note that the file name doesn't have to be
static. You can use any combination of text, variables and data selections; see
"Variable task properties" on page304.
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; for example: "200 OK", "404 Not Found" or "401 Unauthorized".
Choose a response code between 100 and 599. (See: List of HTTP status codes on
Wikipedia.) If the response isn't currently handled by any HTTP response code, you may
use an unused code in that range.
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.
l
Variable containing the response code: The contents of the Job Info variable or
local variable (see "About variables" on page713) selected in this drop-down,
presumed to be a valid response code, will be returned in the response header.
This is the value that is present at the end of the process, not the beginning.
l
Ignore global authentication settings: Disable authentication for this particular URL,
regardless of the global authentication settings. 'Global authentication settings' refers to
the authentication settings of the NodeJS Server, set in the preferences: "NodeJS Server
Input plugin preferences 3" on page799. If authentication is not enabled in the
preferences, this option has no effect.
"Other" Tab
l
Job Information group
l
Information elements: Indicates what Job Info variables are automatically created
by the input task.
Page 360