https://issues.apache.org/bugzilla/show_bug.cgi?id=50377
--- Comment #4 from Christoph Anton Mitterer <[email protected]> 2010-11-29 20:35:58 EST --- Perhaps using: The directives from later ("sections below in the configuration") matching sections (of the same type) override the directives from earlier ("sections above in the configuration") matching sections (of the same type). With the addition that directives from <Directory>s of deeper directories (e.g. /foo/bar) always override directives from <Directory>s of higher directories (e.g. /foo), regardless of the sections ordering within the configuration. However, <Directory> sections of the very same directory (level) are again processed in the order as of the configuration file, as describe above. instead of: Later sections override earlier ones. Describes it more exactly? Ok so? But this still doesn't explain whyAnd why does e.g.: <Location /> Allow from 127.0.0.1 ::1 </Location> <LocationMatch /server-status> SetHandler server-status Order allow,deny </LocationMatch> doesn't lead to an allow, when accessing /server-status... and why: <LocationMatch /server-status> SetHandler server-status Order allow,deny </LocationMatch> <Location /> Allow from 127.0.0.1 ::1 </Location> does !!! *confused* -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
