2020.1

Examples
This task is put into effect in the following example processes:
l HTTP PDF Invoice Request
l HTTP Brochure Request
l Capture Web Manager Workflow
Note that Capture can only be used with PlanetPress Suite.
Known issue
In order to wake up a trigger-based process that starts with the HTTP Server Input task the
server issues a signal to all trigger-based processes, not just those that start with an HTTP
Server Input task. This means that some processes may get woken up when they do not need
to. This issue only occurs in version 2020.1 and will be fixed in version 2020.2.
Input
The HTTP Server Input task does not, by itself, capture any files. Neither does it directly wait
for requests to be received. Actually, it is the HTTP service that receives the requests and
places them in a specific location on the drive. When a request is received, the HTTP Server
Input polls that location and finds the requests and all attachments. It will always pick up the
"oldest" request received.
The request can contain one or more files, one being an XML file containing the request
information as well as any GET or POST variables that were received within this request. Other
files are POST attachments.
Note
By default, the request XML also contains a CDATA section which contains the raw
input data, effectively doubling the size of the incoming file. Due to technical restrictions,
the incoming XML file cannot be more than 400MB, which because of CDATA is reduced
to around 200MB. To help in this situation, you may elect to omit from the attachment,
which can be changed in HTTP Server Input User Options. Please note that incoming
binary files (sent through file upload in a form) can never be larger than 400 MB.
Page 329