8.6

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.
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
First, the output inside the process itself is, depending on the selected options, an XMLrequest
files, 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.
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702.
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
Page 215