> GET /foo/ yields the listing for /foo/, and NopHandler logs > $r->location to the error log as /foo. > > GET /foo/bar yields the results of NopResponse (which just coughs > up its $r->location, /foo/bar), and NopHandler logs $r->location > as /foo/bar, even though it is registered in <Location /foo>. > > GET /foo/bar/bitz yields the same results as GET /foo/bar.
those are all exactly what I would expect. remember that for nested <Location> blocks settings are merged - it doesn't matter that your PerlTypeHandler is registered to /foo, for the URL /foo/bar it is merged with <Location /foo/bar> and it is (ultimately) <Location /foo/bar> (and it's parent configurations) that service the request. but fear not, you're not alone in not understanding how nested container directives behave. but this might help: http://httpd.apache.org/docs/sections.html --Geoff
