2022.2

c:\PReS\http and your Resource action name is static, pointing your browser to
http://127.0.0.1:8080/static/css/style.css will immediately load and return the file
c:\PReS\http\css\style.css . This does not require any process to work - everything is
handled directly by the HTTP Server Input and files are returned immediately. This feature is
very useful when dealing with stylesheets, images, browser JavaScript, or static HTML files that
do not require any processing.
Note: It is possible to serve a default HTML file when no action is specified, for example
http://localhost:8080/ . This is done by creating an index.html file in the Resource
Folder defined above. However, resources called by this index.html must still use the
Resource action name, for example a stylesheet would still point to
http://127.0.0.1:8080/static/css/style.css or more simply stat-
ic/css/style.css.
You also need to take into consideration the options inside each of your processes that start with the
HTTP Server Input task, as they will greatly impact how this process responds. In the process's prop-
erties, the following options will modify HTTP behavior:
l
Self-Replicating Process: This option is critically important when dealing with HTTP processes.
Basically, this means that when HTTP requests are received, the process will duplicate itself up
to the specified maximum number, in order to simultaneously (and asynchronously) handle mul-
tiple requests. See "Process properties" on page721 for more details.
l
As soon as possible: This option needs to be checked, otherwise requests will not be handled
as they come in (this option is meant to be used on scheduled processes that run at intervals).
l
Polling Interval (sec): This option determines how much time the HTTP Server Input waits
between the moment it finishes processing a request and the moment it picks up a new request.
This should be put at 0 in order to process requests as soon as possible, meaning immediately.
And finally, the HTTP Server Input task properties. While these are described in the "HTTP Server
Input" on page601 task properties page, here are a few considerations to keep in mind when using this
task:
l
The HTTP Action corresponds precisely to the name immediately following the first slash of your
address. That is to say, placing the action myaction here means the process would be triggered
by opening http://127.0.0.1:8080/myaction in your browser.
l
The HTTP service accepts both POST and GET requests. Other than the presence of file attach-
ments, there is little difference in how these are handled. This means that visiting /my-
action?id=12345&q=test would be the same as having a form with two <input> fields
named, respectively, id and q, and submitting them with the information "12345" and "test". In
Page 223