[opensuse-factory] apache config -- old and new syntax
Hello list, although we have access_compat compiled in, old syntax is not valid always. Brilliant example is bug 925956[1]. Even worse, conditional approach does not work fully as expected, too[2]. It is so because we use new syntax in httpd.conf unconditionally, for example to deny to /. But, to allow of both layers is needed if both active[3]. The proposal is to go with sle12 solution[4], i. e. make access_compat shared and unloaded by default, which means old syntax will not be accepted until access_compat is loaded to restore previous behaviour. All apache2 package conf would contain <IfModule !mod_access_compat.c> new syntax </IfModule> <IfModule mod_access_compat.c> old syntax </IfModule> to allow go back with access_compat. Suggestions? Petr For details, see: [1] https://bugzilla.suse.com/show_bug.cgi?id=925956 [2] https://bugzilla.suse.com/show_bug.cgi?id=881506#c7 [3] https://bugzilla.suse.com/show_bug.cgi?id=881506#c18 [4] osc cat SUSE:SLE-12:GA apache2 apache2-README-access_compat.txt
Am 21.05.2015 um 11:55 schrieb Petr Gajdos:
Hello list,
although we have access_compat compiled in, old syntax is not valid always. Brilliant example is bug 925956[1]. Even worse, conditional approach does not work fully as expected, too[2].
It is so because we use new syntax in httpd.conf unconditionally, for example to deny to /. But, to allow of both layers is needed if both active[3].
The proposal is to go with sle12 solution[4], i. e. make access_compat shared and unloaded by default, which means old syntax will not be accepted until access_compat is loaded to restore previous behaviour.
All apache2 package conf would contain
<IfModule !mod_access_compat.c> new syntax </IfModule> <IfModule mod_access_compat.c> old syntax </IfModule>
to allow go back with access_compat.
Suggestions?
Petr
For details, see: [1] https://bugzilla.suse.com/show_bug.cgi?id=925956 [2] https://bugzilla.suse.com/show_bug.cgi?id=881506#c7 [3] https://bugzilla.suse.com/show_bug.cgi?id=881506#c18 [4] osc cat SUSE:SLE-12:GA apache2 apache2-README-access_compat.txt
I agree with this proposal, because most apache documentation didn't expect that mod_access_compat is compiled in. Theredore the apache 2.4 behavior in openSUSE seems strange. Stefan -- www.invis-server.org Stefan Schäfer Ludwigstr. 1-3 63679 Schotten -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday 21 May 2015 11.55:42 Petr Gajdos wrote:
Hello list,
although we have access_compat compiled in, old syntax is not valid always. Brilliant example is bug 925956[1]. Even worse, conditional approach does not work fully as expected, too[2].
It is so because we use new syntax in httpd.conf unconditionally, for example to deny to /. But, to allow of both layers is needed if both active[3].
The proposal is to go with sle12 solution[4], i. e. make access_compat shared and unloaded by default, which means old syntax will not be accepted until access_compat is loaded to restore previous behaviour.
All apache2 package conf would contain
<IfModule !mod_access_compat.c> new syntax </IfModule> <IfModule mod_access_compat.c> old syntax </IfModule>
to allow go back with access_compat.
Suggestions?
Petr
For details, see: [1] https://bugzilla.suse.com/show_bug.cgi?id=925956 [2] https://bugzilla.suse.com/show_bug.cgi?id=881506#c7 [3] https://bugzilla.suse.com/show_bug.cgi?id=881506#c18 [4] osc cat SUSE:SLE-12:GA apache2 apache2-README-access_compat.txt
go for it, long time ago when 2.4 appears, I simply put a few minutes to review all my configuration and adjust them to new syntax. The worst to track is 3rd party package who insist on all syntax, but they're in the process to be more and more 2.4 syntax aware or friendly. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot
participants (3)
-
Bruno Friedmann -
Petr Gajdos -
Stefan Schäfer