[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: country codes and content negotiation

On Thu, 24 Aug 2000, James A. Treacy wrote:

> This must be something that others have encountered. Is there a way of
> solving this that avoids us creating symlinks for each variation?

How about type-map files?  Quoting from the Apache manual

Using a type-map file

A type map is a document which is associated with the handler named
type-map (or, for backwards-compatibility with older Apache
configurations, the mime type application/x-type-map). Note that to use
this feature, you must have a handler set in the configuration that
defines a file suffix as type-map; this is best done with a

  AddHandler type-map var

in the server configuration file. See the comments in the sample config
file for more details. 

Type map files have an entry for each available variant; these entries
consist of contiguous HTTP-format header lines. Entries for different
variants are separated by blank lines. Blank lines are illegal within an
entry. It is conventional to begin a map file with an entry for the
combined entity as a whole (although this is not required, and if present
will be ignored). An example map file is:

  URI: foo

  URI: foo.en.html
  Content-type: text/html
  Content-language: en

  URI: foo.fr.de.html
  Content-type: text/html;charset=iso-8859-2
  Content-language: fr, de

In this case, try an entry like

  URI: foo.en.html
  Content-type: text/html
  Content-language: en, en-uk, en-us, en-redneck, en-jive, etc...

I don't know if this will work though, because a little later on in the
explanation, the docs say:

     The languages of the variant, specified as an Internet standard
language tag from RFC 1766 (e.g., en for English, kr for Korean, etc.). 

Are language variants part of RFC 1766?  Does Apache even bother to
check?  I dunno.

Erik Rossen                         ^
rossen@freesurf.ch                 /e\
http://www.multimania.com/rossen   ---   GPG key ID: 2935D0B9

Reply to: