#27323 [Bgs]: use of Apache 2.0 and PHP 4.3.4 on a Solaris production system
| From: | irchtml@php.net | Date: | Sat, 21 Feb 2004 03:58:52 +0000 |
| Subject: | #27323 [Bgs]: use of Apache 2.0 and PHP 4.3.4 on a Solaris production system | ||
| References: | 1 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969359124@lists.php.net to get a copy of this message | ||
ID: 27323
Updated by: irchtml@php.net
Reported By: wzaccone at telcordia dot com
Status: Bogus
Bug Type: Documentation problem
Operating System: Apache 2.0
PHP Version: 4.3.4
New Comment:
Yes, Apache 2 was only released 4 years ago (stable-2 years ago). It
is far too new to even think about supporting it.
The general procedure is to release a major build and ask questions
later.
Submit again before PHP 6 goes into beta testing.
Previous Comments:
------------------------------------------------------------------------
[2004-02-20 21:58:16] sniper@php.net
Apache 2 is still too new. And the SAPI modules we have for it have
proven to be quite buggy too..
And you don't get pretty much anything extra out of Apache2 compared to
Apache1.3 anyway. Enabling Apache2 with threaded MPM, like worker,
makes it really unstable due to 3rd party stuff being non-thread-safe.
Ask again next year. :)
------------------------------------------------------------------------
[2004-02-19 17:45:18] wzaccone at telcordia dot com
Description:
------------
We still see the following warning on php.net in the installation
section of the online documentation: "Do not use Apache 2.0 and PHP in
a production environment neither on Unix nor on Windows. ". My
question: Is this warning still in effect for all releases of PHP???
Is warning the documentation still appropriate in our situation--
specifically PHP 4.3.4 on UNIX/Solaris 8 with Apache 1.3.27. We are
considering migrating to Apache 2.0 on Solaris 8. THANK YOU.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=27323&edit=1