10.1

Page 11
We have divided our example
into three parts. To begin with,
the HTTP Server Input task
waits for requests. When a
request is received, the next
task down stores the request’s
parameters in a variable. The
variable’s content is then
processed to remove any
malicious code. The following
task completes the
document’s path by adding the
location of the server where
the document is actually
stored.
The next part of
the process
checks whether
the requested
document can be
found or not. If
the requested
document is less
than one kilobyte
in size, we assume
it is nonexistent.
When this is the
case, a File Not
Found document
is created, sent to
the requesting client, and then deleted from the server.
If the requested document is more than one
kilobyte in size, then we know it does exist.
In the third part of our process, the
document is actually sent to the requesting
client. The document is first loaded,
renamed to the original name included in the
request (the full path is reduced to the file
name), and sent to the client. Finally, the
document is deleted from the server.
Downloaded PDF documents can then be
opened for viewing, and HTML documents
can be used to collect information that can then be sent back for processing.