On Tue, 2017-02-21 at 21:58 +0000, Joe Orton wrote: > Any reason <IfDirective> is a bad idea, so we can do that more cleanly > (... in a couple of decades time)?
One reason it might be a very bad idea: user confusion! I'm thinking of the track record of <IfModule> here. Our support fora are full of users who have seen it in default/shipped config and docs, and treat it as some magic incantation they need. They end up with a problem "why doesn't Foo work?", which they bring to our fora after many hours of tearing their hair. The usual answer: Get rid of all the <IfModule> crap, to stop suppressing the error message you need! -- Nick Kew
