Re: Apache 2 and PHP for Production?

Why is there such a reluctance to using Apache 2? For stability issues, PHP should recommend Apache 2 but in prefork mode. Instead of saying Apache 2 is unsupported, just say non prefork mode is not supported. Additionally, if PHP is more acceptable of Apache 2 (in the supported mode), then users will shift away from Apache 1.3 and more resources can be put on Apache 2 (both from the Apache side and the PHP side). While non prefork mode may not be supported until PHP is completely rewritten (modules and all), there's no negativity in moving to Apache 2 prefork. Everyone who has to support both Apache versions will be greatful when 1.3 falls away as most users move over to Apache 2 in time. Steve From: Curt Zirzow <php-general@zirzow.dyndns.org> Date: Mon, 19 Jul 2004 23:05:50 -0400 * Thus wrote Oliver John V. Tibi:

Wow! And come to think of it, how did you do it? Or should I stick

with

Apache1 until there is a viable solution to this upgrade dilemma?

I would stay with stick with apache 1.x. The only reason I would consider apache2 is if there was a module only available in apache2 and no other reasonable solution that can be done otherwise, that your site must have. With apache2, I have one site that runs flawless, the other one has spiratic wierd things happen that are unexplainable. If you have an OS that installs apache2 by default (not to mention any names) I would recomend an 'rpm delete apache2' and install manually :)