From a42d626bf5c18ca195a201433599ef1a5047417d Mon Sep 17 00:00:00 2001 From: Stefan Eissing Date: Fri, 21 Oct 2016 09:35:18 +0000 Subject: [PATCH] update after xml change git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1765975 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/howto/http2.html.en | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/docs/manual/howto/http2.html.en b/docs/manual/howto/http2.html.en index 9655e390a7..ac912a0299 100644 --- a/docs/manual/howto/http2.html.en +++ b/docs/manual/howto/http2.html.en @@ -39,6 +39,7 @@
  • HTTP/2 in Apache httpd
  • Build httpd with HTTP/2 support
  • Basic Configuration
  • +
  • MPM Configuration
  • Clients
  • Useful tools to debug HTTP/2
  • Server Push
  • @@ -159,6 +160,25 @@ how to manage multiple hosts with the same certificate.

    top
    +

    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.

    +
    top
    +

    Clients

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