Re: mod_proxy_http2 sni ?

2017-02-23 Thread Steffen


Sent to your email address.


On Thursday 23/02/2017 at 10:24, Stefan Eissing  wrote:

Steffen,

can you get a http2:trace2 log of such a curl request?



Am 22.02.2017 um 12:52 schrieb Steffen :

Picking up the good host now.

With a download chrome says in Status bar: starting, and stays there.

Curl hanging:

   0 14.4M0 327670 0  27237  0  0:09:17  0:00:01  
0:09:16 27237
 0 14.4M0 327670 0  14873  0  0:17:01  0:00:02  
0:16:59 14873
 0 14.4M0 327670 0  10230  0  0:24:44  0:00:03  
0:24:41 10230
 0 14.4M0 327670 0   7796  0  0:32:28  0:00:04  
0:32:24  7796
 0 14.4M0 327670 0   6297  0  0:40:12  0:00:05  
0:40:07  6297
 0 14.4M0 327670 0   5282  0  0:47:55  0:00:06  
0:47:49 0
 0 14.4M0 327670 0   4539  0  0:55:46  0:00:07  
0:55:39 0
 0 14.4M0 327670 0   3987  0  1:03:29  0:00:08  
1:03:21 0





 0 14.4M0 327670 0   3554  0  1:11:13  0:00:09  
1:11:04 0
 0 14.4M0 327670 0   3206  0  1:18:57  0:00:10  
1:18:47 0
 0 14.4M0 327670 0   2920  0  1:26:41  0:00:11  
1:26:30 0


Looks like that the issue is that the front is h2 and the back h2c.

On Wednesday 22/02/2017 at 11:30, Stefan Eissing wrote:


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



Am 17.02.2017 um 16:11 schrieb Steffen :

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 
 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 :


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

bytes GmbH
Hafenstrasse 16
48155 Münster
http://www.greenbytes.de





Stefan Eissing

bytes GmbH
Hafenstrasse 16
48155 Münster
http://www.greenbytes.de






Stefan Eissing

bytes GmbH
Hafenstrasse 16
48155 Münster
http://www.greenbytes.de





Re: mod_proxy_http2 sni ?

2017-02-23 Thread Stefan Eissing
Steffen,

can you get a http2:trace2 log of such a curl request?

> Am 22.02.2017 um 12:52 schrieb Steffen :
> 
> Picking up the good host now.
> 
> With a download chrome says in Status bar: starting, and stays there.
> 
> Curl hanging:
> 
>  0 14.4M0 327670 0  27237  0  0:09:17  0:00:01  0:09:16 27237
>   0 14.4M0 327670 0  14873  0  0:17:01  0:00:02  0:16:59 14873
>   0 14.4M0 327670 0  10230  0  0:24:44  0:00:03  0:24:41 10230
>   0 14.4M0 327670 0   7796  0  0:32:28  0:00:04  0:32:24  7796
>   0 14.4M0 327670 0   6297  0  0:40:12  0:00:05  0:40:07  6297
>   0 14.4M0 327670 0   5282  0  0:47:55  0:00:06  0:47:49 0
>   0 14.4M0 327670 0   4539  0  0:55:46  0:00:07  0:55:39 0
>   0 14.4M0 327670 0   3987  0  1:03:29  0:00:08  1:03:21 0
> 
> 
> 
> 
>   0 14.4M0 327670 0   3554  0  1:11:13  0:00:09  1:11:04 0
>   0 14.4M0 327670 0   3206  0  1:18:57  0:00:10  1:18:47 0
>   0 14.4M0 327670 0   2920  0  1:26:41  0:00:11  1:26:30 0
> 
> Looks like that the issue is that the front is h2 and the back h2c.
>  
> On Wednesday 22/02/2017 at 11:30, Stefan Eissing wrote: 
>> You can try now in v1.9.1 if it works as needed now.
>> 
>>> Am 17.02.2017 um 16:11 schrieb Steffen :
>>> 
>>> 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 
  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 :
> 
> 
> 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
 
 bytes GmbH
 Hafenstrasse 16
 48155 Münster
 http://www.greenbytes.de
 
>>> 
>> 
>> Stefan Eissing
>> 
>> bytes GmbH
>> Hafenstrasse 16
>> 48155 Münster
>> http://www.greenbytes.de
>> 
> 
> 

Stefan Eissing

bytes GmbH
Hafenstrasse 16
48155 Münster
www.greenbytes.de



Re: mod_proxy_http2 sni ?

2017-02-22 Thread Steffen


Picking up the good host now.

With a download chrome says in Status bar: starting, and stays there.

Curl hanging:


0 14.4M0 327670 0  27237  0  0:09:17  0:00:01  
0:09:16 27237
 0 14.4M0 327670 0  14873  0  0:17:01  0:00:02  
0:16:59 14873
 0 14.4M0 327670 0  10230  0  0:24:44  0:00:03  
0:24:41 10230
 0 14.4M0 327670 0   7796  0  0:32:28  0:00:04  
0:32:24  7796
 0 14.4M0 327670 0   6297  0  0:40:12  0:00:05  
0:40:07  6297
 0 14.4M0 327670 0   5282  0  0:47:55  0:00:06  
0:47:49 0
 0 14.4M0 327670 0   4539  0  0:55:46  0:00:07  
0:55:39 0
 0 14.4M0 327670 0   3987  0  1:03:29  0:00:08  
1:03:21 0





 0 14.4M0 327670 0   3554  0  1:11:13  0:00:09  
1:11:04 0
 0 14.4M0 327670 0   3206  0  1:18:57  0:00:10  
1:18:47 0
 0 14.4M0 327670 0   2920  0  1:26:41  0:00:11  
1:26:30 0


Looks like that the issue is that the front is h2 and the back h2c.


On Wednesday 22/02/2017 at 11:30, Stefan Eissing  wrote:

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



Am 17.02.2017 um 16:11 schrieb Steffen :

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 
 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 :


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

bytes GmbH
Hafenstrasse 16
48155 Münster
http://www.greenbytes.de





Stefan Eissing

bytes GmbH
Hafenstrasse 16
48155 Münster
http://www.greenbytes.de





Re: mod_proxy_http2 sni ?

2017-02-22 Thread Stefan Eissing
You can try now in v1.9.1 if it works as needed now.

> Am 17.02.2017 um 16:11 schrieb Steffen :
> 
> 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  
>> 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 :
>>> 
>>> 
>>> 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
>> 
>> bytes GmbH
>> Hafenstrasse 16
>> 48155 Münster
>> www.greenbytes.de
>> 
> 

Stefan Eissing

bytes GmbH
Hafenstrasse 16
48155 Münster
www.greenbytes.de



Re: mod_proxy_http2 sni ?

2017-02-17 Thread Steffen
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  
> 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 :
>> 
>> 
>> 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
> 
> bytes GmbH
> Hafenstrasse 16
> 48155 Münster
> www.greenbytes.de
> 



Re: mod_proxy_http2 sni ?

2017-02-16 Thread Stefan Eissing
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 :
> 
> 
> 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

bytes GmbH
Hafenstrasse 16
48155 Münster
www.greenbytes.de



mod_proxy_http2 sni ?

2017-02-16 Thread Steffen


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