> Am 20.01.2017 um 09:45 schrieb [email protected]: > > Author: elukey > Date: Fri Jan 20 08:45:40 2017 > New Revision: 1779578 > > URL: http://svn.apache.org/viewvc?rev=1779578&view=rev > Log: > Added more details to mod-proxy-http2's doc > > Modified: > httpd/httpd/trunk/docs/manual/mod/mod_proxy_http2.xml > > Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy_http2.xml > URL: > http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy_http2.xml?rev=1779578&r1=1779577&r2=1779578&view=diff > ============================================================================== > --- httpd/httpd/trunk/docs/manual/mod/mod_proxy_http2.xml (original) > +++ httpd/httpd/trunk/docs/manual/mod/mod_proxy_http2.xml Fri Jan 20 08:45:40 > 2017 > @@ -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> >
Not correct. Maybe my explanation was not good. mod_proxy_http2 will always use HTTP/2 in the backend connection. That connection will however only do one request at a time if the frontend is HTTP/1.1. > <p>This module relies on <a href="http://nghttp2.org/";>libnghttp2</a> > to provide the core http/2 engine.</p> > >
