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

Configuration Directives
iTP Secure WebServer System Administrator’s Guide—522659-001
A-31
Negotiation
If there are multiple items in the extension-list, use blanks to separate the items.
Use the following MIME types to enable special server features:
application/x-imagemap
This MIME type specifies that the server process the file as an image map.
application/x-httpd-guardian
This MIME type specifies that the server process the file as a CGI program.
You can set as many MimeType directives as you need to specify the type information
for all the file types on your server. MimeType directives for many common file
extensions are supplied with the server in the file conf/mime-types.config.
For a complete list of MIME types supported by the iTP WebServer, see Example 8-1
on
page 8-8. For more information about MIME types, refer to the Bibliography on
page -xxx.
Default
If there is no matching MIME file for a requested file, the server returns the default
MIME type specified by the DefaultType directive.
Negotiation
Syntax
Negotiation { None | Lang | Mult }
Description
Use the Negotiation directive to specify the how the iTP WebServer will select
from available representations of a requested page. For example, if the same content is
available in multiple languages, the server can provide the content in the user’s preferred
language. Content negotiation is defined in the HTTP/1.1 specification; the iTP Secure
WebServer supports server-driven content negotiation, as described in that document.
The multiview negotiation option is not defined in the HTTP/1.1 specification but is a
feature of the Apache HTTP/1.1 server.
If you specify the argument None, the server does not perform content negotiation. In
this case, if the file requested by the client is not present at the specified URL, the server
returns an error status (404) to the client, reporting that the resource is missing.
If you specify the argument Lang, the server selects content based on a language tag. A
language tag consists of an RFC 2068 language abbreviation, optionally followed by a
hyphen and a subtag; a subtag can be either an RFC 2068 country code or some other
Note. The mapping of extensions to MIME types in the configuration file that comes with your
server is in lowercase. Therefore an extension expressed in uppercase, such as .HTML, will be
processed as text unless you explicitly map the uppercase extension to the correct MIME type.