On Tue, Jul 11, 2017 at 9:13 AM, Hajo Locke <Hajo.Locke@xxxxxx> wrote: > > Am 11.07.2017 um 15:58 schrieb Eric Covener: >> >> On Tue, Jul 11, 2017 at 9:41 AM, David Copeland >> <david.copeland@xxxxxxxxxx> wrote: >>>> >>>> o HTTP/2 will not be negotiated when using the Prefork MPM >>> >>> I'm wondering what the reason for this is? >> >> In the previous release, HTTP2 made prefork run multi-threaded. People >> often chose prefork due to non-threadsafe code running in the server. >> >> > so we cant use http/2 in 2.4.27 when using mod_prefork? it is not > configurable? > We use mod_prefork because of mod_php. Please also note, mod_php has been strongly discouraged for years. The conventional advise is to configure the php fcgi sapi, using either mod_proxy_fcgi with php fpm, or mod_fcgid, and a modest number of single process php fcgi workers to serve requests, and either event or worker MPM. This is still not spelled out well in the formal PHP docs (but who reads docs?) --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|