httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <>
Subject Re: Multi Language Error Documents
Date Sun, 19 Aug 2001 22:28:58 GMT
That sounds like a job for ForceDefaultLanguage then, eh?

ForceDefaultLanguage off  (no touchee)
ForceDefaultLanguage parent  (ok... en for en-us is better than nothing)
ForceDefaultLanguage nomatch  (better serve our DefaultLanguages)
ForceDefaultLanguage full  (Alrightie, try en for en-us, then our DefaultLanguages)

How does this sound?


----- Original Message ----- 
From: "Joshua Slive" <>
To: <>
Sent: Sunday, August 19, 2001 5:18 PM
Subject: RE: Multi Language Error Documents

> <quote>
> >And a little nit...
> >
> >Apart from the security and performance concerns of having multiviews on
> >by default, there's the little problem I've noticed that recent MSIE
> >vintages seem to be sending "en-us" as its default language, not "en", so
> >the distributed config should really have
> >AddLanguage en-us .en
> absolutely -1.  See my detailed answer to Rich Bowen's question on 
> httpd-docs.
> >added to the list so as to not confuse newcomers at the splash screen,
> >they don't get the index.html.en by default.
> They should.  We should fall back on foo if foo-var isn't found.  If that's
> not happening, we have a bug.
> </quote>
> Hmmm... Before you go coding anything, I think you should
> carefully read
> I am not a language lawyer, but the way I interpret that
> is if the browser wants "en", it must ask for "en".
> This page:
> agrees with me under the section "Language Subset Selections"
> and the author (Alan Flavell) is generally trustworthy
> on such topics.
> Joshua.
> _________________________________________________________________
> Get your FREE download of MSN Explorer at

View raw message