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 <[email protected]> wrote: > 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 configuration; also you may want to >> try enabling proxy_ignore_client_abort in the nginx backend [1]. >> >> >> >> cheers, >> lukas >> >> >> [1] >> http://nginx.org/en/docs/http/ngx_http_proxy_module.html#pro >> xy_ignore_client_abort >> >> On 21 February 2018 at 15:29, Sander Klein <[email protected]> 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 >>> {host.name.tld|Mozilla/5.0 >>> (Mac||https://referred.name.tld/some/string?f=%7B%22la_la_la >>> %22:%7B%22v%22:%22thingy%22%7D%7D} >>> {} "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? >>> >>> Greets, >>> >>> Sander >>> >>
