> Am 20.01.2017 um 10:35 schrieb Luca Toscano <toscano.l...@gmail.com>: > > > > 2017-01-20 10:11 GMT+01:00 ste...@eissing.org <ste...@eissing.org>: > > > Am 20.01.2017 um 09:45 schrieb elu...@apache.org: > > > > 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. > > No no it is me being slow to understand HTTP/2 related things :) > > So mod-proxy-http2 will always use HTTP/2 with a "capable" backend, but it > will not exploit its full potential when the frontend requests are HTTP/1.1 > (for example "translating" multiple proxied HTTP/1.1 requests into HTTP/2 > streams over the same TCP connection). > > Better? If not I can revert everything and leave you do it, might be better :)
Nonono. No easy way out: :) You got it right, except one tiny detail: the backend *needs* to talk HTTP/2, there is no fallback to HTTP/1.1 by mod_proxy_http2. Which might be a feature for the future, or a folding of http/2 support into mod_proxy_http (far future). > > Thanks for the patience! Thanks for helping! > > Luca Stefan Eissing <green/>bytes GmbH Hafenstrasse 16 48155 Münster www.greenbytes.de
