I'm experiencing a strange problem with MultiViews on Apache - is
greatly appreciated!


Configuration: Apache 1.3.33 on Debian Linux / P4


Description:

The directory contains PHP-scripts in different languages:

index.php.en
index.php.zh
index.php.fr
index.php.de
index.php.nl

Auto-negotiation works fine for all these languages if 'index' is requested,
except for .zh (Chinese). So even if 'zh' has the highest q-factor in the
HTTP_ACCEPT_LANGUAGE-string, the second match is returned instead of the
first, 'zh'.

In other words, if 'zh' has the highest q-factor and 'en' the second-highest
in the request URI, then 'index.php.en' is returned instead of
'index.php.zh'.

Does anybody have a clue of what is going on here?

- Yes, I did 'AddLanguage zh .zh' in httpd.conf;
- Yes, I did 'httpd reload' after that;
- Yes, I tried all sorts of variations with documents and .conf-settings like
'zh-CN', 'zh-HK', 'zh-TW' etcetera.


Again, is greatly appreciated. Thanks!


-- Jorn Mineur <jorn@mineur.net>

On Sun, 20 Mar 2005 23:53:25 +0100, Alan J. Flavell wrote
(in message <Pine.LNX.4.61.0503202227440.13474@ppepc56.ph.gla. ac.uk>):

> On Sun, 20 Mar 2005, Jorn Mineur wrote:

>> Auto-negotiation works fine for all these languages if 'index' is
>> requested, except for .zh (Chinese).

> I honestly don't know the answer to your problem, but let's at least
> explore some possibilities...

Thank you very much, Alan, for these suggestions.

<blush>
I have spent the whole morning experimenting, then, after realizing that
apache was disregarding *any* changes I made to httpd.conf, found the rather
trivial solution: 'apachectl restart' instead of 'apache reload'.
</blush>

-- Jorn Mineur <jorn@mineur.net>

On Mon, 21 Mar 2005, Jorn Mineur wrote:

> <blush>
> I have spent the whole morning experimenting, then, after realizing
> that apache was disregarding *any* changes I made to httpd.conf,
> found the rather trivial solution: 'apachectl restart' instead of
> 'apache reload'.
> </blush>

Don't worry, I've made equivalent mistakes myself. Thanks for sharing
the solution, anyway - it's always more satisfying to see that a
problem has been resolved - no matter what the explanation may have
turned out to be.

It rather supports my contention that .htaccess is a better place for
experimenting. Though one might need to clear the browser cache
afterwards.