Hi guys,
On Thu, Feb 22, 2018 at 11:24 AM, Sander Klein wrote:
> It was indeed the option httpclose enabled only on that backend.
I tried to reproduce the issue but failed to do so. The config I used
is this one :
listen h2
mode http
bind :4443 ssl crt
Maybe this should be a warning when starting haproxy? So people doesn't
configure h2 wrong?
On Thu, Feb 22, 2018 at 11:24 AM, Sander Klein wrote:
> Thanks Lukas,
>
> It was indeed the option httpclose enabled only on that backend.
>
> Greets,
>
> Sander
>
>
> On 2018-02-21
Thanks Lukas,
It was indeed the option httpclose enabled only on that backend.
Greets,
Sander
On 2018-02-21 16:49, Lukas Tribus wrote:
Hello Sander,
make sure you use "option http-keep-alive" as http mode, specifically
httpclose will cause issue with H2.
If that's not it, please share the
Hello Sander,
make sure you use "option http-keep-alive" as http mode, specifically
httpclose will cause issue with H2.
If that's not it, please share the configuration; also you may want to
try enabling proxy_ignore_client_abort in the nginx backend [1].
cheers,
lukas
[1]
Hi All,
Today I tried enabling http/2 on haproxy 1.8.4. After enabling all
requests to a certain backend started to give 400's while requests to
other backend worked as expected. I get the following in haproxy.log:
Feb 21 14:31:35 localhost haproxy[22867]:
5 matches
Mail list logo