|
Posted by Jerry Stuckle on 10/29/07 11:22
AnrDaemon 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?
>
You should read EVERYTHING I said - and not take things out of context.
>> Everything in the world does not belong in your httpd.conf, directly or
>> indirectly. It is the Apache configuration file, not the PHP, Perl,
>> MySQL and the rest-of-the-world configuration file. It should be used as
>> such - for configuring Apache and things which are specific to the
>> server, a virtual host or a directory.
>
> Loading PHP as apache module making it in fact part of Apache, so I configure
> Apache module from httpd.conf. What's wrong?
> Or You just want a place to spread Your idealism? Sorry, I'm not a good
> target for Your lessons.
>
>
No, loading PHP as an apache module makes it an EXTENSION of Apache.
You should configure Apache in httpd.conf and PHP in php.ini. That's
what they are there for.
Sorry, when I see someone post something this asinine, I'll call you on
it. Just because you're being an idiot doesn't mean the entire world
should be.
Let's see you show me where ZEND or Apache recommend you do it this way.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
Navigation:
[Reply to this message]
|