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

Configuring the iTP Secure WebServer
iTP Secure WebServer System Administrator’s Guide—522659-001
7-14
Mapping Requests to Contents
If the request does not contain an AcceptLanguage header, the server uses the value
or values of the LanguagePreference directive to condition the search. If the
configuration does not include a LanguagePreference directive, the server returns a
status code indicating that the file was not found.
3. After locating a subdirectory for the preferred language, the server searches for and
returns the requested file. If the server finds a directory corresponding to the highest
weighted language, but the file is not present in that directory, the server searches
for the file in the directory for the second best language, then the third best, and so
on. Most browsers specify ‘any language’ (*) as the final language tag in the
Accept-language header to increase the likelihood that some file will be returned.
To use language-only content negotiation, you define a separate subdirectory for each
language; use the RFC 2068 standard abbreviation for the language as the subdirectory
name; and store the files that contain text in each language in the corresponding
subdirectory. For information about RFC 2068, use the following URL:
http://www.csl.sony.co.jp/rfc/mirror/rfc2068.txt
Multiview. If the configuration specifies multiview content negotiation (Mult), the
server examines the request URL and then:
1. If the requested file is present at the specified location (as determined by the URL
and any applicable Filemap directives), the server returns the file. No content
negotiation occurs.
2. If the requested file is not present at the specified location, the server searches for a
file whose extensions match the criteria specified by the request headers.
The Accept header specifies the preferred content types. The MIME types table
(Example 8-1, Server MIME Types,
on page 8-8) defines the corresponding file
extensions. If the request does not contain an Accept header, the server does not
select content on the basis of content type.
The Accept-language header or the LanguagePreference directive specifies the
preferred languages: the LanguagePreference directive applies only if the request
has no Accept-language header. The LanguageSuffix directive defines the
corresponding file extensions. If the request does not contain an Accept-language
header and the configuration file does not contain a LanguagePreference directive,
or if the configuration file does not contain a LanguageSuffix directive for any
preferred language, the server does select content on the basis of language.
The Accept-encoding header specifies the preferred encodings. the MIME types
table (Example 8-1, Server MIME Types,
on page 8-8) defines the corresponding
file extensions. If the request does not contain an Accept-encoding header, the server
does not select content on the basis of encoding.
3. Upon locating a file that meets the content-negotiation criteria, the server returns
that file to the client.