Re: Re: PHPINIDir directive
| From: | Aaron Bannert | Date: | Mon, 22 Apr 2002 20:28:25 +0000 |
| Subject: | Re: Re: PHPINIDir directive | ||
| References: | 1 2 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-83169@lists.php.net to get a copy of this message | ||
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 override the 1st override, as it were :)
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
console/logs. Maybe we should just write a better PHPINIDir error message?
-aaron