From: Stefan Eissing Date: Fri, 21 Oct 2016 09:34:56 +0000 (+0000) Subject: added mpm advice to http2 howto X-Git-Tag: 2.5.0-alpha~1080 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=fac9b336ca32e85ae1203281949f985837ff7575;p=apache added mpm advice to http2 howto git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1765974 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/howto/http2.xml b/docs/manual/howto/http2.xml index 27c806286b..9e1eeb2de3 100644 --- a/docs/manual/howto/http2.xml +++ b/docs/manual/howto/http2.xml @@ -154,6 +154,25 @@ ProtocolsHonorOrder Off how to manage multiple hosts with the same certificate.

+
+ MPM Configuration + +

HTTP/2 is supported in all multi-processing modules that come with httpd. However, if + you use the prefork mpm, there will be severe restrictions.

+

In prefork mod_http2 will only process one request at at time + per connection. But clients, such as browsers, will send many requests at the same time. + If one of these takes long to process (or is a long polling one), the other requests will + stall.

+

mod_http2 will not work around this limit by default. The reason is that + prefork is today only chosen, if you run processing engines that re not + prepared for multi-threading, e.g. will crash with more than one request.

+

If your setup can handle it, configuring event mpm is nowadays + the best one (if supported on your platform).

+

If you are really stuck with prefork and want multiple requests, + you can tweak the H2MinWorkers to make + that possible. If it breaks, however, you own both parts.

+
+
Clients

Almost all modern browsers support HTTP/2, but only over SSL connections: Firefox (v43),