iTP Secure WebServer System Administrators Guide (Version 7.5+)

PathwayMimeMap tcltcl-server
PathwayMimeMap userapp/G/UA
PathwayMimeMap userapp2/G/UA:ua2-server
The next set of examples displays the relationship between a PathwayMimeMap directive and the
corresponding MimeType directive. The MimeType directive must precede the PathwayMimeMap
directive but does not have to appear directly before it as shown. The two MimeType directives
indicate that files with the extension cgiand ab_demo have the MIME type application
x/httpd-guardian. The corresponding PathwayMimeMap directives indicate that files with
the extension cgi are processed by the generic-cgi server class, and files with the extension
ab_demo are processed by a server class under control of the PATHMON process /G/ZAB or
$ZAB.
MimeType application x/httpd-guardian cgi
PathwayMimeMap cgi generic-cgi
MimeType application/x-httpd-guardian ab_demo
PathwayMimeMap ab_demo /G/ZAB
Pidfile
Syntax
PidFile filename
Description
You set the PidFile directive to the file in which the server is to record the serverprocess ID.
The PidFile directive is optional. Only one PidFile directive is allowed in the configuration
file.
Default
None. If you do not set the PidFile directive, no process ID file is written.
Example
PidFile /usr/tandem/webserver/httpd.pid
PutScript
Syntax
PutScript CGI-script-filename
Description
Use the PutScript directive to indicate that you want the iTP Secure WebServer to support the
PUT method defined by the HTTP/1.1 protocol. The PUT method stores a new page or replaces
an existing page on the host.
If you do not include this directive, a client can upload content to the host by using the File Transfer
Protocol (FTP) or the POST request method. The differences in operation among FTP, POST, and
PUT are:
• FTP copies a file to a specified location. Filemap directives in your configuration file determine
the correspondence between URLs and file locations on the server.
• POST sends data, for example input from a form, to the resource specified by the URL in the
request. For example, the URL could identify an application that accepts data, a gateway that
forwards data, or a resource such as a newsgroup or a database that can have items added
to it.
• PUT differs from POST in that the content sent in the request is stored under the specified URL,
replacing any content that might have been store there previously.
Pidfile 231