Re: http2-issue with http2 enabled on frontend and on backend

2019-02-28 Thread Willy Tarreau
Hi Tom, On Wed, Feb 27, 2019 at 07:45:04AM +0100, Tom wrote: > Hi Willy > > I've applied your patch and now the website responds with http2..., many > thanks for this. > > The current situation looks like this: > > - When I directly connect with http2 to the nginx, which has >

Re: http2-issue with http2 enabled on frontend and on backend

2019-02-26 Thread Tom
Hi Willy I've applied your patch and now the website responds with http2..., many thanks for this. The current situation looks like this: - When I directly connect with http2 to the nginx, which has server-side-pushing enabled, my browser receive this push-traffic (without any GET-requests

Re: http2-issue with http2 enabled on frontend and on backend

2019-02-26 Thread Willy Tarreau
> > 3) When I enable "http2_push_preload on;" on the nginx (because nginx wants > > to push images etc.) then the website is not working and I have the > > following entries in the haproxy-log: > > Feb 26 12:04:50 localhost haproxy[31691]: srcip=1.1.1.1:56146 > >

Re: http2-issue with http2 enabled on frontend and on backend

2019-02-26 Thread Willy Tarreau
On Tue, Feb 26, 2019 at 12:37:11PM +0100, Tom wrote: > Hi Jérôme > > Many thanks for your hint. This solved the initial problem. But there are > other issues regarding http2: > > 1) > When I enable "errorfile 503 /etc/haproxy/503.html" in the defaults-section, > then haproxy comes not up and

Re: http2-issue with http2 enabled on frontend and on backend

2019-02-26 Thread Christopher Faulet
Le 26/02/2019 à 14:12, Tim Düsterhus a écrit : Tom, Am 26.02.19 um 13:10 schrieb Tom: 2) When I enable removing the server-header from the backend with "rspidel ^Server:.*", then the haproxy-workers are terminating with Segmentation fault and the website via haproxy is not working: Does

Re: http2-issue with http2 enabled on frontend and on backend

2019-02-26 Thread Tom
Hi Tim Of course (haproxy-1.9.4): --- schnipp --- global log 127.0.0.1 local1 info chroot /home/haproxy user haproxy group haproxy master-worker ssl-server-verify none tune.ssl.default-dh-param 2048

Re: http2-issue with http2 enabled on frontend and on backend

2019-02-26 Thread Tim Düsterhus
Tom, Am 26.02.19 um 13:10 schrieb Tom: >>> 2) >>> When I enable removing the server-header from the backend with >>> "rspidel ^Server:.*", then the haproxy-workers are terminating with >>> Segmentation fault and the website via haproxy is not working: >> >> Does http-response del-header Server

Re: http2-issue with http2 enabled on frontend and on backend

2019-02-26 Thread Tom
On 26.02.19 12:57, Jarno Huuskonen wrote: Hi, On Tue, Feb 26, Tom wrote: 1) When I enable "errorfile 503 /etc/haproxy/503.html" in the defaults-section, then haproxy comes not up and logs the following error: "Unable to convert message in HTX for HTTP return code 503." Does it work if you

Re: http2-issue with http2 enabled on frontend and on backend

2019-02-26 Thread Jarno Huuskonen
Hi, On Tue, Feb 26, Tom wrote: > 1) > When I enable "errorfile 503 /etc/haproxy/503.html" in the > defaults-section, then haproxy comes not up and logs the following > error: > "Unable to convert message in HTX for HTTP return code 503." Does it work if you move the errorfile 503 to

Re: http2-issue with http2 enabled on frontend and on backend

2019-02-26 Thread Tom
Hi Jérôme Many thanks for your hint. This solved the initial problem. But there are other issues regarding http2: 1) When I enable "errorfile 503 /etc/haproxy/503.html" in the defaults-section, then haproxy comes not up and logs the following error: "Unable to convert message in HTX for

Re: http2-issue with http2 enabled on frontend and on backend

2019-02-26 Thread Jerome Magnin
On Tue, Feb 26, 2019 at 11:19:12AM +0100, Tom wrote: > Hi list > > When I enable health-checks on the backend, then the backend comes not up, > because of "Layer7 invalid response". The backend is a simple nginx with > http2 enabled. As I mentioned: When I directly talk to the backend with >

Re: http2-issue with http2 enabled on frontend and on backend

2019-02-26 Thread Jerome Magnin
On Tue, Feb 26, 2019 at 11:19:12AM +0100, Tom wrote: > Hi list > > I'm using haproxy-1.9.4 and trying to enable http2 in frontend and on one > backend server (nginx with http2 enabled). I'm always receiving a http/502 > from haproxy. I'm successfully able to directly talk to the backend with >

http2-issue with http2 enabled on frontend and on backend

2019-02-26 Thread Tom
Hi list I'm using haproxy-1.9.4 and trying to enable http2 in frontend and on one backend server (nginx with http2 enabled). I'm always receiving a http/502 from haproxy. I'm successfully able to directly talk to the backend with http2, but not via haproxy. The haproxy-log looks like this