Message: 15
Date: Wed, 30 Aug 2006 15:13:48 -0400
From: Pete Akins <email@hidden>
Subject: Re: Server Admin - Apache aliases and cases
To: macosx-server <email@hidden>
Message-ID: <email@hidden>
Content-Type: text/plain; charset="us-ascii"
This is a really annoying problem that i have filed a bug report on.
It has happened for as long as I can remember in 10.4.x since we have
Thanks for verifying Pete that it's not just us. This is a bummer.
So Server Admin is off-limits for us for now. What seems bizarre is
that Apple uses all these case-fancy paths -- /Library/WebServer, /
Users/Sites, but then creates an admin tool that disrespects case.
Very annoying.
For us, this came up when installing Lyceum (the multi-user fork of
WordPress), and creating an alias from /blogs (virtual) to /Library/
WebServer/Documents/wwwrooot/include/lyceum/src. Lyceum would then
look in some subdirectory of that location for its own data, e.g. /
blogs/username would be mapped by Lyceum to include/lyceum/src/wp-
content/blogs/3 . And from there, it would try to pull up index.php
-- which is where things probably connect to the Directory override
stuff you mention below.
Anyway, long story short is that this bug breaks applications.
A solution (this would require changes to Apache) would be to have a
directive that turns off case sensitivity for directory matching.
Until then, you have to fix those things by hand and NEVER EVER touch
the web panel of server admin. Bummer eh? I am unaware of such an
option.
This issue makes using any apache install with Xsan require hand
editing since Xsan volumes are case sensitive. OR always use lower
case (which stinks if you have an existing mixed case deployment).
Are you (or is anyone) aware of a way to convince Server Admin to
ignore particular site definitions? We tried renaming ones we don't
SA to overwrite in /etc/httpd/sites and that didn't work - it just
renames them again. Would it be safe to run chflag on some of the
config files we absolutely don't want touched (i.e. sites that
depend on case sensitive aliases)?
Hope this clears things up. Please file an additional bug report on
this so it gets the attention it deserves!
