Thanks Lukas,

It was indeed the option httpclose enabled only on that backend.



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 configuration; also you may want to
try enabling proxy_ignore_client_abort in the nginx backend [1].



On 21 February 2018 at 15:29, Sander Klein <> wrote:
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]:
2001:bad:coff:ee:cd97:5710:4515:7c73:52553 [21/Feb/2018:14:31:30.690]
backend-name/backend-04 1/0/1/-1/4758 400 1932 - - CH-- 518/215/0/0/0 0/0
{} "GET /some/path/here/filename.jpg HTTP/1.1"

The backend server is nginx which proxies to a nodejs application. When
looking at the request on nginx it gives an HTTP 499 error.

Is this a known issue? Or, is this a new H2 related issue?

Anyway I can do some more troubleshooting?



Attachment: 0x2E78FBE8.asc
Description: application/pgp-keys

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to