<title>MPM Configuration</title>
<p>HTTP/2 is supported in all multi-processing modules that come with httpd. However, if
- you use the <code>prefork</code> mpm, there will be severe restrictions.</p>
- <p>In <code>prefork</code> <code>mod_http2</code> will only process one request at at time
+ you use the <module>prefork</module> mpm, there will be severe restrictions.</p>
+ <p>In <module>prefork</module>, <module>mod_http2</module> 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.</p>
- <p><code>mod_http2</code> will not work around this limit by default. The reason is that
- <code>prefork</code> is today only chosen, if you run processing engines that re not
+ <p><module>mod_http2</module> will not work around this limit by default. The reason is that
+ <module>prefork</module> 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.</p>
- <p>If your setup can handle it, configuring <code>event</code> mpm is nowadays
+ <p>If your setup can handle it, configuring <module>event</module> mpm is nowadays
the best one (if supported on your platform).</p>
- <p>If you are really stuck with <code>prefork</code> and want multiple requests,
+ <p>If you are really stuck with <module>prefork</module> and want multiple requests,
you can tweak the <directive module="mod_http2">H2MinWorkers</directive> to make
that possible. If it breaks, however, you own both parts.</p>
</section>