> >Some choice has to be made when merging. If you have something such as:
> >
> >
> >PerlSetVar someKey someValue
> >
> >
> >
> >PerlSetVar someKey otherValue
> >
> >
> >then you issue a request for /foo/bar.thmtl. Both configuration
> >directives apply, so a decision has to be made as to which h
At 22:18 22/11/1999 -0600, Ken Williams wrote:
>But my gripe is with the following:
>
>--docroot/.htaccess:
>
> PerlSetVar Lemon Tasty
>
>
>--docroot/subdir/.htaccess:-
>PerlSetVar Lemon Sour
>
>
>Now i
[EMAIL PROTECTED] (Eric Cholet) wrote:
>Ken Williams wrote:
>> I've done some more digging, and found a rather bizarre explanation.
>> As it turns out, if the parent .htaccess has its directive in a
>> section and the subdirectory doesn't, the parent will
>> override the child. If they're speci
Ken Williams wrote:
> I've done some more digging, and found a rather bizarre explanation. As it
> turns out, if the parent .htaccess has its directive in a section and
> the subdirectory doesn't, the parent will override the child. If they're
> specified the same way, the child will override t
I've done some more digging, and found a rather bizarre explanation. As it
turns out, if the parent .htaccess has its directive in a section and
the subdirectory doesn't, the parent will override the child. If they're
specified the same way, the child will override the parent.
The worst part i
Hi,
I'm wondering about a precedence issue with PerlSetVar. Suppose I have the
following setup:
in docroot/.htaccess:
PerlSetVar Lemon Tasty
in docroot/dir/.htaccess:
PerlSetVar Lemon Sour
Which one is supposed to be present when I request, say, docroot/dir/file.html?
My intui
