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

Configuring the iTP Secure WebServer
iTP Secure WebServer System Administrator’s Guide—523346-002
7-14
Mapping Requests to Contents
•
The LanguageSuffix directive maps between the RFC 2068 standard
abbreviation for a language (such as en-US for American English and de for
German) and the extension used to identify files in that language on the host. For
example, the following directive specifies that German language files will have the
extension .ger:
LanguageSuffix de .ger
For detailed information about these directives, see Appendix A, Configuration
Directives.
To see RFC 2068, use the following URL:
http://www.cis.ohio-state.edu/htbin/rfc/rfc2068.html
Storing Content for Negotiation
To select among different representations of the same content, the server does not
examine the files; rather, it searches for path components or file extensions that
correspond to content-representation options. The server behaves very differently
depending on whether the Negotiation directive specifies language-only (Lang),
multiview (Mult), or no (None) content negotiation. In fact, you must store your content
differently depending on the kind of negotiation you choose.
Language Only. If the configuration species language-only content negotiation (Lang),
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 subdirectory whose name is the RFC 2068 standard abbreviation for the
preferred language.
For example, if the request contains the URL:
/us/ca/sj/store1/product.html
and if an AcceptLanguage header specifies English (en) followed by German (de)
as acceptable languages, the server first searches for the subdirectory:
/store1/en/
If no such directory exists, the server searches for the subdirectory:
/store1/de/
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.