# Status for apache 2 and PHP - still not recomendable?

- Thread: https://externals.io/message/23145
- Original archive: https://news-web.php.net/php.internals/23145
- Started by erik@nordicaudi.com on 2006-05-03T19:57:18+00:00
- Messages: 3
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #23145 — erik@nordicaudi.com — 2006-05-03T19:57:18+00:00

URL: https://externals.io/message/23145#23145

Is this still correct?

http://se.php.net/manual/en/install.unix.apache2.php

Or is it recommendable to start using apache 2 in production?

Regards

/Erik

---

## #23148 — D. Walsh — 2006-05-04T06:21:01+00:00

URL: https://externals.io/message/23145#23148 · In reply to: #23145

> Is this still correct?
>
> http://se.php.net/manual/en/install.unix.apache2.php

Reading that page clearly leads me to the following conclusion:

We do not recommend using a threaded MPM in production with Apache2.  
Use the prefork MPM instead, or use Apache1. For information on why,  
read the related FAQ entry on using Apache2 with a threaded MPM


> Or is it recommendable to start using apache 2 in production?
>
> Regards
>
> /Erik

-- Dale

---

## #23190 — steve — 2006-05-08T03:02:22+00:00

URL: https://externals.io/message/23145#23190 · In reply to: #23148

Apache 2 is fine. You can even use threaded MPMs, just use FastCGI.
Personally, I found it to work better than Apache 1.3 with mod_php,
but that's just me...

-steve