diff options
| author | Luca Toscano <elukey@apache.org> | 2017-01-20 12:43:52 +0100 |
|---|---|---|
| committer | Luca Toscano <elukey@apache.org> | 2017-01-20 12:43:52 +0100 |
| commit | 3662aba280d2db405ad233ae735f7f37e431f5b0 (patch) | |
| tree | 0c693d85953584bcf4f645f6e2ac6b989af9a6aa | |
| parent | Reworked mod-proxy-http2's documentation after Stefan's suggestions (diff) | |
| download | apache2-3662aba280d2db405ad233ae735f7f37e431f5b0.tar.xz apache2-3662aba280d2db405ad233ae735f7f37e431f5b0.zip | |
documentation rebuild
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1779610 13f79535-47bb-0310-9956-ffa450edef68
| -rw-r--r-- | docs/manual/mod/mod_proxy_http2.html.en | 29 |
1 files changed, 16 insertions, 13 deletions
diff --git a/docs/manual/mod/mod_proxy_http2.html.en b/docs/manual/mod/mod_proxy_http2.html.en index 4beb2f5d40..8a266c00dd 100644 --- a/docs/manual/mod/mod_proxy_http2.html.en +++ b/docs/manual/mod/mod_proxy_http2.html.en @@ -35,24 +35,27 @@ <tr><th><a href="module-dict.html#SourceFile">Source File:</a></th><td>mod_proxy_http2.c</td></tr></table> <h3>Summary</h3> - <p>This module <em>requires</em> the service of <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>. It provides the features used for - proxying HTTP/2 requests. <code class="module"><a href="../mod/mod_proxy_http2.html">mod_proxy_http2</a></code> - supports HTTP/2 only. It does <em>not</em> - provide any downgrades to HTTP/1.1.</p> + <p><code class="module"><a href="../mod/mod_proxy_http2.html">mod_proxy_http2</a></code> + supports HTTP/2 only, it does <em>not</em> + provide any downgrades to HTTP/1.1. This means that the backend + needs to support HTTP/2 because HTTP/1.1 will not be used instead.</p> - <p>Thus, in order to get the ability of handling HTTP/2 proxy requests, + <p>This module <em>requires</em> the service of <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>, so in order to get the ability of + handling HTTP/2 proxy requests, <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code> and <code class="module"><a href="../mod/mod_proxy_http2.html">mod_proxy_http2</a></code> - have to be present in the server.</p> + need to be both loaded by the server.</p> - <p><code class="module"><a href="../mod/mod_proxy_http2.html">mod_proxy_http2</a></code> works with incoming requests - over HTTP/1.1 and HTTP/2 requests. In both cases, requests proxied - to the same backend are sent over a single connection + <p><code class="module"><a href="../mod/mod_proxy_http2.html">mod_proxy_http2</a></code> works with incoming fronted requests + using HTTP/1.1 or HTTP/2. In both cases, requests proxied + to the same backend are sent over a single TCP connection whenever possible (namely when the connection can be re-used).</p> - <p><code class="module"><a href="../mod/mod_proxy_http2.html">mod_proxy_http2</a></code> will not use the HTTP/2 protocol - when the frontend requests use HTTP/1.1. - This means that HTTP/2 will be used to proxy requests to a capable backend - only when the frontend requests use the same protocol.</p> + <p>Caveat: there will be no attemp to consolidate multiple HTTP/1.1 + frontend requests (configured to be proxied to the same backend) + into HTTP/2 streams belonging to the same HTTP/2 request. + Each HTTP/1.1 frontend request will be proxied to the backend using + a separate HTTP/2 request (trying to re-use the same TCP connection + if possible).</p> <p>This module relies on <a href="http://nghttp2.org/">libnghttp2</a> to provide the core http/2 engine.</p> |