[Inso Home Page] [Home] [Collection] [Book] [Expand] [Collapse] [Search Forms] [Previous Section with Hits] [Next Section with Hits] [Clear Search] [Preferences] [Print] [Help]

 inside  Expand Search


   Configuration Directives   [Table of Contents]

DynaWeb Publishers Guide

[-] Appendix B: The DynaWeb Internet Server
[-] The NSAPIProtocolModule Directives

The NSAPIProtocolModule Directives

This section explains in more detail the different directives that can be configured for each protocol module in use by the server.

ServerName

Syntax

ServerName  <name>

Description

The ServerName is the fully-qualified name of the machine the server is running on.

Example

ServerName  www.inso.com

ServerUser

Note: This is only used on UNIX platforms and only affects the operation of the server if the server is started by the superuser.

Syntax

ServerUser <username>

Description

This directive determines the name under which the server will be running. (i.e. "nobody", "root", etc.)

Example

ServerUser nobody

Port

Syntax

Port <port#>

Description

Determines the port that the module will be listening to for requests.

Note: The first 1024 ports are restricted. If such a port is selected, the server must be started by a superuser or superuser process.

Example

Port  8000

MaxThreads

Syntax

MaxThreads <number>

Description

The value of MaxThreads determines the number of requests that the server can handle simultaneously. A setting of 0 (zero) disables the multithreading features of the server, and all requests are handled sequentially.

Example

MaxThreads  32

NumRequests (Unix Only)

Syntax

NumRequests <number>

Description

Sets the numbers of requests the module will handle before recycling itself.

A setting of 0 (zero) disables the recycling feature.

Example

NumRequests 10000

AccessLog

Syntax

AccessLog </path/to/access.log>

Description

Sets the location of the log file in which to store the access log. The access log records all requests made to the module (and all other modules) and is written in a standard log format.

Example

AccessLog  /pro/server/logs/access.log

Sample output:

255.255.255.255 - - [17/Oct/1996:10:00:00 -0500] "GET / HTTP/1.0"
2000 782

ErrorLog

Syntax

ErrorLog </path/to/error.log>

Description

This directive points to the location of the error log, where the module records errors or informational messages generated by errant requests to the server.

Example

ErrorLog /pro/server/logs/errors.8000

MimeMap

Syntax

MimeMap </path/to/mimetypes>

Description

Sets the location of the mime-types file used by the server. The mime-types file is set up in the format of "type=<some-mime-type> exts=<extension list>" and is named mime.typ.

Example

MimeMap /pro/server/data/config/mime.typ

Sample mimetype:

type=image/jpeg  exts=jpg,jpeg

ObjectFile

Syntax

ObjectFile </path/to/NSAPIconfigurationfile>

Description

Points to the NSAPI configuration file that controls how the NSAPIProtocolModule handles requests. This file is similar to Netscape's obj.conf file. The file is named nsapi.cfg and is located in the data/config directory beneath the server's installation directory.

Example

ObjectFile /pro/server/data/config/nsapi.cfg

ErrorPath

Syntax

ErrorPath <error-directory>

Description

When the module needs to return an HTTP error message in response to a request, it looks in the directory specified by ErrorPath for a file named {error-code}.htm.

Example

ErrorPath /pro/server/data/error

   Configuration Directives   [Table of Contents]