> -----Original Message-----
> From: Matt Sergeant [mailto:[EMAIL PROTECTED]]
> Sent: Monday, December 11, 2000 11:57 AM
> To: Geoffrey Young
> Subject: RE: Still bugs in Apache::Dispatch with .htaccess
>
>
> On Mon, 11 Dec 2000, Geoffrey Young wrote:
>
> >
> >
> > I've started poking around...
> >
> > in order to allow .htaccess configurations we have to be
> able to accomodate:
> > /Foo/Bar/Baz/foo where .htaccess lives in Foo: Prefix +
> > Bar::Baz->foo()
> > /Foo/Bar/Baz/foo where .htaccess lives in Bar: Prefix
> + Baz->foo()
> >
> > yuk. with <Location> you don't have to worry about the
> left hand side...
>
> OK, so how about a new directive: DispatchBase. If that is set, remove
> that from $r->filename, and use that as the base path.
> Otherwise use the
> $r->location method.
yeah, I thought about that too - it would involve less overhead than
scanning for the location of the .htaccess file, but wouldn't be as friendly
as DispatchAccess On.
I also don't want to confuse people, though. The issue here is <Directory>
v. <Location> and not specifically .htaccess files (any more, at least :) -
applying this to a <Location> could start to get obscure (as if it isn't
already :)
DispatchTrim "/usr/local/apache/htdocs/" ?
DispatchBase (which is probably what I should have called DispatchISA) ?
DispatchDirectory ?
or do both that and have a .htaccess scan as well?
--Geoff
>
> --
> <Matt/>
>
> /|| ** Director and CTO **
> //|| ** AxKit.com Ltd ** ** XML Application Serving **
> // || ** http://axkit.org ** ** XSLT, XPathScript, XSP **
> // \\| // ** Personal Web Site: http://sergeant.org/ **
> \\//
> //\\
> // \\
>
