iTP Secure WebServer System Administrator's Guide (Version 7.0)

Configuration Directives
iTP Secure WebServer System Administrator’s Guide—523346-012
A-38
Default
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 Secure WebServer, see
Example 8-1 on page 8-8. For more information about MIME types, see 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 Secure 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 registered code. For example, the code en-US signifies American English, and
the code fr signifies French. The client specifies the preferred language tag or tags in
the Accept-language header; if no such header appears in the request, the server uses
the value or values specified in the LanguagePreference directive. To support this
feature, the target directory must have subdirectories with names corresponding to the
language tags. For example, if the client requests a French language representation of
the page /store1/welcome, the server looks for the file in the directory /store1/fr/.
To see RFC 2068, use this URL:
http://www.cis.ohio-state.edu/htbin/rfc/rfc2068.html