Mailinglist Archive: opensuse (1986 mails)

< Previous Next >
Re: [opensuse] Apache server side includes openSUSE 10.3 x86_64
  • From: Anton Aylward <anton.aylward@xxxxxxxxxx>
  • Date: Fri, 21 Nov 2008 18:30:22 -0500
  • Message-id: <4927448E.3080801@xxxxxxxxxx>
Peter Bradley said the following on 11/21/2008 05:37 PM:
Ysgrifennodd Per Jessen:
Just use the Apache manual and ignore most others.

That makes sense. The only trouble is that I couldn't understand it. I
still don't know if I should have mod_include installed, and if I do how
to do it, or even whether I already have it installed.
You set it up in /etc/sysconfig/apache - there's a variable specifying
which modules to load.

That's one of the most intimidating config files I've ever come across,
so I don't really understand it. It does seem to say that the include
module is installed by default and it does have an entry saying:

APACHE_MODULES="actions alias auth_basic authn_file authz_host
authz_groupfile authz_default authz_user authn_dbm autoindex cgi dir env
expires include log_config mime negotiation setenvif ssl suexec userdir
php5 rewrite dav dav_svn authz_svn"

So, since include in in that list, I would expect to be able to do
server side includes: but I can't.

I'd go further than that. I've added modules there and Apache
complains. Obviously its not as simple as that. Where should the
modules live? Only in /usr/lib/apache2 ? Apparently not. And this is
all openSUSE specific, its not in the Apache manuals.

I use 'AddOutputFilter INCLUDES shtml' instead of the addhandler.

I tried this both in addition to the addhandler and instead of it. When
I had both, there was no change at all. The html was not parsed. When
I replaced AddHandler with AddOutputFilter, the html was parsed, but the
include was not included (i.e. it was just treated as a comment).

I've tried this with fcgi putting it in /etc/sysconfig/apache and in
/etc/apache2/config.d/ without success.

Sorry if it's me that's being thick. Wouldn't be the first time. But
I'd really like to get this going if I can.

I wouldn't call myself an Apache expert, but I've set up it up on many
other implementations of Linux. The way openSUSE has created the set-up
seems to have many non-independent interactions that have to be aligned.
Call this strong or un-necessary "coupling". Other systems have a
simple, single config file. I suspect a lot of this is brought about by
YAST. I do note that the YAST module for Apache seems to ignore any
files you create in vhosts.d/ and doesn't seem to build its list by
scanning what's in /usr/lib/apache2, /usr/lib/apache2-event,
/usr/lib/apache2-prefork and /usr/lib/apache2-worker to see what
modules are available. I've experimented with this and been disappointed.

The killer is that /etc/apache2/sysconfig.d/loadmodule.conf gets rebuilt
on startup. WHY ?? Personally I think that zapping a config file
like that is a bad thing. I'm not saying that there shouldn't be
dynamically built config files, but usually the ones called "*.conf" are
for humans to edit or humans to run an explicit program to change, not
to be altered 'behind the scenes', every time. Call is something else!
Please! Hours wasted editing that because it looked like the closest
thing to the sub-config file that openSUSE had "broken out" rather than
have one single config file like other distributions. Heck, I put stuff
in /etc/sysconfig/apache's LOADMODULES and they were never included
automagically in /etc/apache2/sysconfig.d/loadmodule.conf. Confusing as
all hell.

IOException: Jovian moons misaligned.
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >