You can try now in v1.9.1 if it works as needed now.

> Am 17.02.2017 um 16:11 schrieb Steffen <[email protected]>:
> 
> Looks like the same, is not looking for the host as with 1.1
> 
> It is on my wish list for 2.4.26 
> 
> 
> 
>> Op 16 feb. 2017 om 11:38 heeft Stefan Eissing <[email protected]> 
>> het volgende geschreven:
>> 
>> Is this the same as https://github.com/icing/mod_h2/issues/124 ?
>> 
>> It seems that the ProxyPreserveHost is not (correctly) implemented.
>> 
>>> Am 16.02.2017 um 10:42 schrieb Steffen <[email protected]>:
>>> 
>>> 
>>> Have an Apache ssl only in front of an Apache on port 80 with several 
>>> vhosts.
>>> 
>>> In front have:
>>> 
>>> 
>>> ProtocolsHonorOrder On
>>> Protocols h2 http/1.1
>>> LoadModule http2_module modules/mod_http2.so
>>> 
>>> 
>>> 
>>> ProxyPass         / http://127.0.0.1:80/
>>> ProxyPassReverse / http://127.0.0.1:80/
>>> 
>>> 
>>> In backend have:
>>> 
>>> 
>>> ProtocolsHonorOrder On
>>> Protocols h2c http/1.1
>>> LoadModule http2_module modules/mod_http2.so
>>> 
>>> This is working great and with all the vhosts.
>>> 
>>> 
>>> When I add/change the front to:
>>> 
>>> 
>>> ProtocolsHonorOrder On
>>> Protocols h2 http/1.1
>>> LoadModule http2_module modules/mod_http2.so
>>> LoadModule proxy_http2_module modules/mod_proxy_http2.so
>>> 
>>> 
>>> ProxyPass         / h2c://127.0.0.1:80/
>>> ProxyPassReverse / h2c://127.0.0.1:80/
>>> 
>>> 
>>> This is not working as expected, all is going to the default/first vhost.
>>> 
>>> a log line from the backend gives is all cases not found .
>>> 
>>> default 127.0.0.1 - - [16/Feb/2017:10:22:00 +0100] "GET /index.php 
>>> HTTP/2.0" 404 207 .......
>>> 
>>> 
>>> Cheers,
>>> 
>>> Steffenal
>>> 
>>> 
>> 
>> Stefan Eissing
>> 
>> <green/>bytes GmbH
>> Hafenstrasse 16
>> 48155 Münster
>> www.greenbytes.de
>> 
> 

Stefan Eissing

<green/>bytes GmbH
Hafenstrasse 16
48155 Münster
www.greenbytes.de

Reply via email to