From: Jeremy Nixon <[EMAIL PROTECTED]>
Josh Narins <[EMAIL PROTECTED]> wrote:
> I also tried /foo/bar/blah and tried this once (i.e. it tried /foo/bar,
and
> didn't end up trying simply /foo)
Hmm, wait... you'd said that a request for /foo/bar resulted in the
subrequest for /bar... is it that, or is it looking up /foo -- ie, the
equivalent of dirname("/foo/bar")? The latter sounds more normal, like
it could be something within the normal Apache flow -- mod_dir or
mod_autoindex (which is why I asked about real directories), an auth
module checking the containing directory, etc.
Sorry for the confusion. For random url /foo/bar/baz/blah the second (and
only subsequent) attempt is /bar/baz/blah
Is it breaking anything?
A fixup handler that says "if the url matches /baz/" then do a little work
here. That work ends up getting done twice (including, in just one instance,
saving something to the DB, where I get double entries). For instance,
/object/staff and /otherobject/staff both trigger the same fixup handler,
because $r->uri =~ m#/staff#, regardless of /object or /otherobject at the
beginning.
Maybe it wasn't the soundest design principle in the first place, but, hey,
I wasn't expecting _this_.
_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar get it now!
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
