From d4b8957f1d453ea832f043ac29e89bb716eb4d84 Mon Sep 17 00:00:00 2001 From: Christophe Jaillet Date: Sun, 24 Jun 2018 18:55:12 +0000 Subject: [PATCH] Fix a typo and use instead of in order to have links and a better syntax highlight git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1834258 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/howto/http2.xml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/manual/howto/http2.xml b/docs/manual/howto/http2.xml index ad30e42a17..bba5a4b9cc 100644 --- a/docs/manual/howto/http2.xml +++ b/docs/manual/howto/http2.xml @@ -158,17 +158,17 @@ ProtocolsHonorOrder Off 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 + 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 +

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 are 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 +

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, +

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.

-- 2.40.0