On Thu, Oct 04, 2001 at 09:48:01AM -0400, Adam Di Carlo wrote: > "James A. Treacy" <[EMAIL PROTECTED]> writes: > > > In another mail, you said you are using mozilla. Is the language setting > > 'en' or does it include a country code? > > Yes, it is 'en-us'. > > I just was able to fix it by adding 'en' as an alternative. > > Does that mean this bug is closable or that we have a problem? > Is it a problem? You decide:
Apache closely follows the http/1.1 spec. This means an 'en' variant will not be returned when 'en-us' is requested. On the other hand, an 'en-whatever' variant can be returned when 'en' is requested. Go figure. While apache is technically correct, it is completely unintuitive and causes problems when using content negotiation with every browser that uses country codes by default (which is a lot - even though the http spec cautions against this). I filed a bug against apache (upstream) about this years ago, asking that apache be configurable to do the Right Thing (even if it is officially wrong). I tried various means of convincing apache (using the config files) to serve the en variant when en-us or en-gb are requested, but they didnt' work. What I'm sure will work is to create symlinks for every file: foo.en-us.html -> foo.en.html foo.en-uk.html -> foo.en.html and then add the following to the apache config AddLanguage en-us .en-us AddLanguage en-uk .en-uk plus add en-us en-uk to LanguagePriority As a test, I set up the above by hand for the sitemap file. You will see that it now works as you want it to, i.e. you could go back to using the (broken) en-us. Does anyone want to set up the above for the whole web site? You would think that we could simply use: AddLanguage en .en AddLanguage en-us .en AddLanguage en-uk .en but apache only allows a 1-1 mapping on file extensions (the last one listed is used). On a related note, does anyone know what is more commonly used: en-uk or en-gb? I've seen both. -- James (Jay) Treacy [EMAIL PROTECTED]
