Aaron Bannert wrote:
>
> Aha, ok I see what you mean now. Is there a way to tell the difference
> between multiple "peer" directives and a merged vhost directive?
> We could detect this in the server merge function, but there is
> no way that I know of for sending a meaningful message back to the
On Mon, Apr 22, 2002 at 04:23:27PM -0400, Jim Jagielski wrote:
> Guess I wasn't clear :)
>
> If httpd.conf includes:
>
>PHPINIDir "foo"
>.
>.
>.
>PHPINIDir "bar"
>
>
> The latter isn't allowed, and assumes a Vhost reason. I wonder if,
> instead, we should allow the 2nd to o
Aaron Bannert wrote:
>
> On Mon, Apr 22, 2002 at 04:01:25PM -0400, Jim Jagielski wrote:
> > Right now, we assume that each successive use of PHPINIDir is
> > due to its inclusion in a . I wonder if
> > that's overly restrictive... Should we allow successive uses and
> > just honor the last one?
>
On Mon, Apr 22, 2002 at 04:01:25PM -0400, Jim Jagielski wrote:
> Right now, we assume that each successive use of PHPINIDir is
> due to its inclusion in a . I wonder if
> that's overly restrictive... Should we allow successive uses and
> just honor the last one?
Since the PHPINIDir is supposed to
