8.4

For HTTPSSupport information, see HTTP Server Input User Options.
Note
While you can insert the HTTPServer Input task anywhere in your process as a secondary input
task, in reality the HTTPServer Input task will only function when used as the initial input, as it is
triggered when PReS Workflow HTTPServer receives a request and passes it on to the correct task.
Warning
It is highly recommended to make all processes using the HTTP Server Input task self-replicating and
to reduce their polling interval in the Process Properties.
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.
Technical
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 CDATA from the attachment, which can be changed in HTTP Server
Input User Options. Please note that this limitation also affects incoming binary files (sent through file
upload in a form), regardless of CDATA settings.