I haven't gotten around to fixing yet, but I (or someone) will annotate accordingly. On Apr 5, 2016 8:00 AM, "Hildegard Meier" <daku8...@gmx.de> wrote:
> Thanks, > > that is correct, it was absoluteley not clear to me that having the module > "access_compat" enabled and mixing old and new style would be absoluteley > not supported. > > Would be clearer, if the new style directives would lead to errors when > having "access_compat" enabled, I guess. > > So I would suggest to make the 2.2->2.4 Upgrade guide ( > https://httpd.apache.org/docs/2.4/upgrading.html) clearer regarding this. > > I disabled now the "access_compat" module and converted all the old style > directives to the new style in one (big) step, and now everything is > working as before. > > Initially, I wanted to do the conversion stepwise, and that let to the > initial problem. > > Best regards > > *Gesendet:* Dienstag, 05. April 2016 um 13:15 Uhr > *Von:* "Rich Bowen" <rbo...@rcbowen.com> > *An:* docs@httpd.apache.org > *Betreff:* Re: Aw: Re: Guide for Upgrade from 2.2 to 2.4: Need to mention > default rule "<Directory /> Require all denied" > > > You _must_ pick one or the other. Either use compat, or unload it. If you > have compat loaded, it expects the "old" format. > > I thought we had made this clear in the doc but apparently not. > > Recommended best practice, of course, is to use the new syntax. Compat > things always result in long term confusion in exchange for your short term > convenience. > --------------------------------------------------------------------- To > unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org For additional > commands, e-mail: docs-h...@httpd.apache.org
