8.7

checked, it means there is a second output that comes out of the HTTPServer Input task:The
last output generated by PlanetPress Workflow is sent back to the initial input, which is returned
back to the client.
Note
Starting in version 7.2 of PlanetPress Workflow, you can now serve static resources
through PlanetPress, which is especially useful for images, CSSand JavaScript files.
See "HTTPServer Input 2 plugin preferences" on page710.
HTTP Server input task properties are as follows:
l
HTTP action: Enter the name of the action requested of PlanetPress Workflow by the
client. This name corresponds to the URLthat the client will be accessing. For example, if
you enter "MakePDF" here, you could trigger the process by accessing
http://127.0.0.1:8080/MakePDF . This is also what your HTMLForm's action should be.
l
MIME Type: Select the MIME type that best suits the files PlanetPress Workflow will be
receiving as input.
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, but most
browsers will interpret it as plain text.
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".
Page 222