iTP Secure WebServer System Administrator's Guide (iTPWebSvr 6.0+)

Using Common Gateway Interface (CGI) Programs

iTP Secure WebServer System Administrator’s Guide—523346-002

8-10

Server Class Configuration

You use the Server directive to establish the configuration of the generic-CGI server

class or a Pathway CGI server class. The configuration files shipped with the iTP

Secure WebServer include Server directives for the generic-CGI server class, the

Servlet Server class (SSC), and the Antarctic Bank demonstration application. You can

change the configuration of these server classes by changing the Server directives

that define them. For example, you might want to change the number of processes in a

server class.

The following example, from the default configuration file httpd.config, defines the

generic-CGI server class with a default set of server attributes:

Server generic-cgi.pway {eval $DefaultServerAttributes}

The server class name is derived from the name in the Server directive by stripping the

.pway extension. The URL httpd://www.server.com/generic-cgi.pway

becomes a generic-CGI server class.

When adding a Pathway server class, do not use the same file name under different

directories. File names must translate to a legal server class name as follows:

•

The server class name is less than or equal to 15 characters.

•

The first character must be alphabetic.

•

The underscore character is illegal in a Pathway server class name.

For a detailed description of the Server directive, see Appendix A, Configuration

Directives. For specific information about defining new SSCs, see Section 9, Using

NonStop Servlets for JavaServer Pages (NSJSP).

# added for XML support

MimeType text/xmlxml XML

MimeType text/xslxsl XSL

# Encoding Types (for compression)

EncodingType x-gzipgz

EncodingType x-zip-compressZ

# Everything below this point has been added for version 2.0

MimeType audio/x-pn-realaudio ra ram

Example 8-1. Server MIME Types (page3of3)