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

Configuration Directives
iTP Secure WebServer System Administrator’s Guide—523346-012
A-39
Default
If an Accept-Language header is present, the server searches for a subdirectory that
matches a language tag in that header. To specify precedence among the tags,
HTTP/1.1 defines the concept of a q value for each tag; the server searches for
subdirectories in order of descending q value. If no q values are specified, the server
searches for subdirectories in the order in which the language tags occur in the
Accept-language header.
If you specify the argument Mult, the server selects content based not only on a
language tag, but also on other headers in the request, matching the specified criteria
to file extensions (not subdirectories) in the target directory. For example, if the client
requests a French language, HTML representation of the page /store1/welcome, the
server expects the file to be named /store1/welcome.fr.html or /store1/welcome.html.fr.
If no file matches all the criteria specified in the request, the server weighs the criteria,
from highest to lowest priority as:
•
Content or media type (such as audio/basic, text/html) from the Accept header
•
Natural language (such as en, de) from the Accept-language header
•
Content encoding (such as compress, gzip) from the Accept-encoding header
If the request does not include an Accept-language header, the server uses the values
given in the LanguagePreference directive.
To use different content-negotiation policies in different regions of a WebServer
environment, use Negotiation as a Region command.
Default
If you omit this directive, the default value is None (no content negotiation).
Example
Assume that you specified the argument Mult and that the directory janedoe contains
the files xyz.html, xyz.en.html, and xyz.gif.
A client requests the URL /usr/janedoe/xyz with the following Accept headers:
•
Accept:image/jpeg, text/html, */*
•
Accept-language:en, fr, es
•
Accept-encoding: gzip
To service the request, the server finds all files whose names begin with “xyz,” then
uses the request headers to select the best match. In this case, the best match is
xyz.en.html, which satisfies the criteria in the Accept and Accept-language headers.
Note. To use language as a criterion for multiview content negotiation, you must include a
LanguageSuffix directive to map each language tag to a file extension.