Re: Apache delivering the wrong file
On Sun, Jun 18, 2006 at 06:36:51PM +0200, Frank Lichtenheld wrote:
> But what real benefits do you see in using it?
Primarily WRT language negotiation:
ForceLanguagePriority can be used to avoid "406 Not Acceptable" errors for
users with badly configured browsers (e.g. no English in the browser list).
"Not Acceptable" is a bit of a problem as users might interpret it as "You
have done something bad".
(Incidentally, this 406 problem can also prevent Google from indexing a
site. However, this is mostly a problem for PHP+MultiViews+Apache1, see
Additionally, Apache 2 contains an (IMHO) important fix for the issue of
e.g. "es" vs "es-ar": In the case that a user only has "es-ar" (Spanish as
spoken in Argentina) in his preferences, Apache 1 will *not* serve the "es"
(Spanish) version of the page, but give a 406. Apache 2 will serve the "es"
version. This type of misconfiguration is very common. The browsers are the
ones not behaving according to spec, they should automatically add the
non-country-specific version of the language. *sigh*
Finally, Apache 2 allows you to do language negotiation via cookies. This
means that our language selection links at the bottom of each page could be
made to permanently select the language: After clicking on such a link, a
user can navigate on to further pages and still see the content in the
language he selected earlier, without reconfiguring the browser. Config
|_) /| Richard Atterer | GnuPG key: 888354F7
| \/¯| http://atterer.net | 08A9 7B7D 3D13 3EF2 3D25 D157 79E6 F6DC 8883 54F7
¯ '` ¯