Posted by luiheidsgoeroe on 10/29/07 11:08

On Oct 29, 11:05 am, AnrDaemon <anrdae...@freemail.ru> wrote:
> Greetings, Jerry Stuckle.
> In reply to Your message dated Saturday, October 27, 2007, 18:02:01,
>
>
>
> > AnrDaemon wrote:
> >> Greetings, Jerry Stuckle.
> >> In reply to Your message dated Saturday, October 27, 2007, 18:15:16,
>
> >>> I always use php.ini to set the basic commands. I'll use the httpd.conf
> >>> to modify specific directories for specific commands, but that's all.
>
> >>> It's stupid to load all of your configuration stuff in httpd.conf. And
> >>> even worse to put it in .htaccess!
>
> >> We're speaking about specific needs (say, handling dynamic signatures and file
> >> downloads).
>
> >> Why I said
>
> >>>> Use php-apache2handler.ini or php-apache2filter.ini (depends on which SAPI You
> >>>> use) to create default environment.
>
> > Try your full comment:
> > >>> Hm. Please tell me why You bothering with PHP.ini if You using PHP
> > >>> as web scripting engine?
>
> > >>> Install PHP as Apache module and use httpd.conf/.htaccess to control
> > >>> it's behaviour.
>
> > >>> Use php-apache2handler.ini or php-apache2filter.ini (depends on
> > >>> which SAPI You use) to create default environment.
> > I restate. It is stupid to place everything in your httpd.conf,
>
> You're indeed right. Any better comments?
>
> > directly or indirectly by placing it in a file called in your
> > httpd.conf. PHP.INI is the initialization file for PHP, and should be
> > used as such.
>
> Well, please, how I can change PHP/Apache behaviour in single directory using
> one PHP.ini?

As he states:

> > It (httpd.conf) should be used as
> > such - for configuring Apache and things which are specific to the
> > server, a virtual host or a directory.

I suspect you actually agree...
--
Rik

[Back to original message]