2021.1

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.
Processing
Depending on the options chosen in the HTTP Server Input task properties, the task may
choose to ignore some of the files. For example, using the "Do not include XML envelope"
means that only the POST attachments will be used in the process, the XML file will be
discarded. Attachments are always saved on disk in a specific location, which is accessible
either directly in the XML or directly as a data file through the "Loop each attachment as data
file" option.
Output
At first, the output inside the process itself is, depending on the selected options, an XML
request file, POST Attachments files, either one or both.
If the Send Immediate Response to client option is selected, the response file is sent back
right away and the involvement of the input task ends then.
However, if this option is not 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 (see "Request/process/response cycle" on
page283).
Even if the process ends with a "Delete" on page652 task, it is still returned to the client;
deleting the job file only means you are not doing anything with it locally.
Note
You can serve static resources through PlanetPress, which is especially useful for
images, CSS and JavaScript files. See "HTTP Server Input plugin preferences 2" on
Page 332