summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLuca Toscano <elukey@apache.org>2017-01-20 08:45:40 +0000
committerLuca Toscano <elukey@apache.org>2017-01-20 08:45:40 +0000
commit2aa27cf8c07f93e024f13ee89b5aa3326c869ed2 (patch)
tree62458a39849825877558cce754a9f2d60908bac2
parent526ae59d909b91c650205cf1659cedb1e5e286b2 (diff)
downloadhttpd-2aa27cf8c07f93e024f13ee89b5aa3326c869ed2.tar.gz
Added more details to mod-proxy-http2's doc
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1779578 13f79535-47bb-0310-9956-ffa450edef68
-rw-r--r--docs/manual/mod/mod_proxy_http2.xml11
1 files changed, 8 insertions, 3 deletions
diff --git a/docs/manual/mod/mod_proxy_http2.xml b/docs/manual/mod/mod_proxy_http2.xml
index d6bcae9aa2..710172401c 100644
--- a/docs/manual/mod/mod_proxy_http2.xml
+++ b/docs/manual/mod/mod_proxy_http2.xml
@@ -41,9 +41,14 @@
have to be present in the server.</p>
<p><module>mod_proxy_http2</module> works with incoming requests
- over HTTP/1.1 and HTTP/2 requests. If <module>mod_http2</module>
- handles the frontend connection, requests against the same HTTP/2
- backend are sent over a single connection, whenever possible.</p>
+ over HTTP/1.1 and HTTP/2 requests. In both cases, requests proxied
+ to the same backend are sent over a single connection
+ whenever possible (namely when the connection can be re-used).</p>
+
+ <p><module>mod_proxy_http2</module> 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>This module relies on <a href="http://nghttp2.org/">libnghttp2</a>
to provide the core http/2 engine.</p>