www/apache
1
0
Fork 0
mirror of https://github.com/apache/httpd.git synced 2025-08-01 07:26:57 +03:00
Code Activity

documentation rebuild

Browse Source 
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1830489 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Luca Toscano
2018-04-29 05:58:52 +00:00
parent 6647764e3b
commit c17a9471f6
7 changed files with 64 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/manual/mod/mod_proxy_http2.html.en
View File

@ -51,7 +51,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
@ -78,6 +78,7 @@
<ul id="topics">
<li><img alt="" src="../images/down.gif" /> <a href="#examples">Basic Examples</a></li>
<li><img alt="" src="../images/down.gif" /> <a href="#notes">Request notes</a></li>
<li><img alt="" src="../images/down.gif" /> <a href="#h2push">HTTP/2 PUSH</a></li>
</ul><h3 class="directives">Directives</h3>
<p>This module provides no
directives.</p>
@ -123,6 +124,19 @@ ProxyPassReverse "/app" "http://app.example.com"</pre>
<dt>proxy-status</dt>
<dd>The HTTP/2 status received from the backend server.</dd>
</dl>
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="h2push" id="h2push">HTTP/2 PUSH</a><a title="Permanent link" href="#h2push" class="permalink">&para;</a></h2>
<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>
</div>
</div>
<div class="bottomlang">