Re: Multiple connections to the same URL with H2

> On 20 Aug 2018, at 16:40, Aleksandar Lazic wrote: > > Hi. > > Am 20.08.2018 um 15:28 schrieb Ing. Andrea Vettori: >> Hello, >> >> we’re using haproxy since version 1.7 for our websites. Backends are mostly >> Apache Tomcat. We have a centralised log s

Multiple connections to the same URL with H2

is then interrupted ? Thank you -- Ing. Andrea Vettori Responsabile Sistemi Informativi

Re: Multiple connections to the same URL with H2

rver and the client terminated > first > by the client. Since this happens only since we enabled H2 on haproxy, can we assume that this is caused by the client closing the connection? Or can this be related to how haproxy handles H2 and convert it to multiple http1 calls ? Thank

Re: Multiple connections to the same URL with H2

Hello, Anyone can please help me to understand if this is normal behaviour caused by clients when using H2 or if there’s something that must be fixed on haproxy configuration or something else ? Any help or hint to docs to read would be very appreciated. Thanks — Ing. Andrea Vettori Responsabile

Re: Truncated response on 2.0.8

> On 28 Oct 2019, at 11:51, Christopher Faulet wrote: > > Le 26/10/2019 à 18:10, Ing. Andrea Vettori a écrit : >> Hello, >> I'm using haproxy 2.0.8 and ssl termination with h2 and http1.1 protocols. >> Since today we always used http1.1 on the backends.

Re: Truncated response on 2.0.8

he-control: no-store, must-revalidate, max-age=0 < pragma: no-cache < expires: Sat, 26 Jul 1997 05:00:00 GMT < content-type: text/html;charset=UTF-8 < content-language: en-US < date: Tue, 29 Oct 2019 08:49:39 GMT < { [8192 bytes data] 100 479k0 479k0 0 5581k 0 --:--:-- --:--:-- --:--:-- 5646k * Connection #0 to host g.testhost left intact Thanks — Ing. Andrea Vettori Responsabile Sistemi Informativi

Re: Truncated response on 2.0.8

> On 28 Oct 2019, at 22:00, Christopher Faulet wrote: >> macbookpro:~ andreavettori$ curl --http1.1 -v http://g.testhost > [SNIP] > Here there is a problem with your configuration. Don't know what, but HAProxy > closed abruptly the client connection. Could you provide your default and > global

Re: Truncated response on 2.0.8

> On 29 Oct 2019, at 10:20, Christopher Faulet wrote: > Please consider to use nghttp if possible. Curl does not give enough details > at the protocol layer. Also enable HTTP logs (option httplog in your defaults > section and the info level on the log line in your global section instead of >

Truncated response on 2.0.8

-servers backend dev-ssl-servers server webdev 10.2.2.50:8083 maxconn 750 proto h2 backend dev-servers server webdev 10.2.2.50:8080 maxconn 750 proto h2 — Ing. Andrea Vettori Responsabile Sistemi Informativi

Re: Truncated response on 2.0.8

> On 31 Oct 2019, at 10:02, Christopher Faulet wrote: > > Le 29/10/2019 à 18:48, Ing. Andrea Vettori a écrit : >> Here is a direct session to backend server from the client machine in clear >> text http2 without upgrade. Note that in this case output is NOT tr

Question on logging only specific hosts

that are not matching the ACL; I think they are related to connections that are not valid so they do not reach reading the “Host” header. Is there a way to invert the process and start “silent” and then enable “info” with an ACL ? Thank you! — Ing. Andrea Vettori Sistemi Informativi B2BIres s.r.l.