Bug ID 1023616
Summary APACHE_CONF_INCLUDE_DIRS order change wrt. loadmodules, from 13.1 to tumbleweed
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Apache
Assignee bnc-team-apache@forge.provo.novell.com
Reporter patrick.schaaf@yalwa.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Noticed an issue when upgrading from 13.1 to tumbleweed, wrt. apache
configuration.

I was using the sysconfig APACHE_CONF_INCLUDE_DIRS variable to draw in all my
virtual host configuration.

With 13.1 and older, the sysconfig.d/loadmodules.conf is included _before_ the
config selected by APACHE_CONF_INCLUDE_DIRS (sysconfig.d/include.conf), by
explicit ordering in the standard httpd.conf

With tumbleweed, the whole sysconfig.d directory is no longer referenced in
httpd.conf, but instead selected with an explicit "-C 'Include
/etc/apache2.d/sysconfig.d/'" command line option. And .conf files from that
directory, are then included in alphabetic order - which especially means
include.conf comes _before_ loadmodules.conf

That change became an issue to me, because the config I drew in via
include.conf, was using <IfModule> stanzas - but these are apparently order
dependant, and the module I tested for, was not yet loaded -> operation fail.

I worked around the issue by simply stopping use of APACHE_CONF_INCLUDE_DIRS,
and instead putting my stuff in the usual vhosts.d/ directory. In that case the
order works out right - and as vhosts.d is included by httpd.conf, that shows
that the '-C Include sysconfig.d' runs even fully before httpd.conf.

While the issue is solved for me with that workaround, I thought it might be
useful to make this bug report, in case somebody else runs into the same
issues, or a maintainer might want to do something about it.


You are receiving this mail because: