Hi Luke. Am 30.01.2019 um 12:58 schrieb Luke Seelenbinder: > Hi Aleks, > > You're correct for http/1.1, but unfortunately, nothing I found after a > pretty long search indicated 1.8.x supports an h2 frontend with reusable > backend connections (h1.1 or h2).
Looks like You are also right for h2 case. I haven't seen h2 in Marco's configuration therefor I haven't assumed he use h2. Let's see what's Marco's answer is ;-) > I stuck with h/1.1 until 1.9 was released because of this. > > Best, > Luke Regards Aleks > — > Luke Seelenbinder > Stadia Maps | Founder > stadiamaps.com > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > On Wednesday, January 30, 2019 12:02 PM, Aleksandar Lazic > <[email protected]> wrote: > >> Hi. >> > >> Am 30.01.2019 um 11:53 schrieb Marco Corte: >> > >>> Il 2019-01-30 11:40 Luke Seelenbinder ha scritto: >>> > >>>> Are you on 1.9.x? 1.8.x does not support reuse of backend connections >>>> when using an h2 frontend. 1.9.x does support this and it works quite >>>> nicely. >>> > >>> Yes! I am on version 1.8.17. >>> Thank you for the explanation! >> > >> Well somehow it supports >> https://cbonte.github.io/haproxy-dconv/1.8/configuration.html#4-http-reuse >> > >> I would play with the timeouts >> > >> https://cbonte.github.io/haproxy-dconv/1.8/configuration.html#4-timeout >> http-keep-alive >> https://cbonte.github.io/haproxy-dconv/1.8/configuration.html#4-timeout >> http-request >> > >> There are some more timeouts which starts in the doc at `timeout check` in >> this section. >> https://cbonte.github.io/haproxy-dconv/1.8/configuration.html#4.1 >> > >> never the less 700ms is "relatively" long so I would also add a check in the >> server line. >> > >>> .marcoc >> > >> Regards >> Aleks >
