mod_proxy_http2 docs: added section about HTTP/2 PUSH implementation and alternatives.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1830443 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/mod/mod_proxy_http2.xml b/docs/manual/mod/mod_proxy_http2.xml
index 5cf16dd64b31075c537224b5d0f4737a0e1fb0cb..ab7954034128cc4d6edef3be595e3055ab9dd08f 100644 (file)
--- a/docs/manual/mod/mod_proxy_http2.xml
+++ b/docs/manual/mod/mod_proxy_http2.xml
@@ -46,7 +46,7 @@
     to the same backend are sent over a single TCP connection
     whenever possible (namely when the connection can be re-used).</p>
 
-    <p>Caveat: there will be no attemp to consolidate multiple HTTP/1.1 
+    <p>Caveat: there will be no attempt 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
@@ -116,4 +116,17 @@ ProxyPassReverse "/app" "http://app.example.com"
     </dl>
 </section>
 
+<section id="h2push"><title>HTTP/2 PUSH</title>
+    <p>The module does not support the HTTP/2 feature PUSH. Backend servers
+    that would like to advertise preload resources should send the appropriate 
+    <code>Link</code> headers.</p>
+    <p>If available, they may do so using the <code>"103 Early Hints"</code> 
+    intermediate responses as specified in 
+    <a href="https://tools.ietf.org/html/rfc8297">RFC 8297</a>. This will give
+    the best performance. If the client is talking HTTP/2 as well, this may
+    then result in a PUSH from Apache to the client or just in forwarding
+    the 103 response.</p>
+    
+</section>
+
 </modulesynopsis>