On Tue, Feb 21, 2017 at 4:58 PM, Joe Orton <jor...@redhat.com> wrote: > For cases like HttpProtocolOptions where a new directive is introduced > to multiple active branches simultaneously, it gets awkward to use > <IfVersion> to write conf files which use the new directive but are > compatible across multiple versions. > > Triggered by a conversation with a user, but also e.g. see current test > suite t/conf/extra.conf.in which breaks for 2.4 releases older than > 2.4.25 with: > > <IfVersion >= 2.2.32> > <VirtualHost _default_:http_strict> > DocumentRoot @SERVERROOT@/htdocs/ > HttpProtocolOptions Strict Require1.0 RegisteredMethods > > Any reason <IfDirective> is a bad idea, so we can do that more cleanly > (... in a couple of decades time)? > > Regards, Joe
Seems pretty neat.
