Re: Truncated response on 2.0.8

Le 31/10/2019 à 11:01, Ing. Andrea Vettori a écrit : Sorry to bother you with all these stuff. But for now, I don't know where to start my investigation. Sure I’ll do as soon as possibile and thank you very much for your continued support. Hi, Sorry for the delay and thanks for the

Re: Truncated response on 2.0.8

On Thu, Oct 31, 2019 at 11:01:06AM +0100, Ing. Andrea Vettori wrote: > Is it normal that the data frame with END_STREAM has zero length on haproxy > responses while it's > 0 (1 actually) on the direct connection ? It simply corresponds to a late shutdown. It's the normal way of closing when you

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 truncated >> if I call the

Re: Truncated response on 2.0.8

On Thu, Oct 31, 2019 at 10:02 AM Christopher Faulet wrote: > Could you provide the result of the following command, executed on HAProxy > server ? > >tcpdump -i any -w h2toh2.cap port 82 or port 8080 Better add -s0, otherwise you may only get 68 bytes (at least on older tcpdump releases).

Re: Truncated response on 2.0.8

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 truncated if I call the command without the ‘-n’ option. To do this test I temporary overriden the

Re: Truncated response on 2.0.8

Le 29/10/2019 à 15:33, Ing. Andrea Vettori a écrit : 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

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 >

Re: Truncated response on 2.0.8

Le 29/10/2019 à 09:54, Ing. Andrea Vettori a écrit : On 29 Oct 2019, at 09:39, Christopher Faulet > wrote: Le 28/10/2019 à 22:00, Christopher Faulet a écrit : macbookpro:~ andreavettori$ curl --http2 -v http://g.testhost [SNIP] Here, it is the expected behavior.

Re: Truncated response on 2.0.8

> On 29 Oct 2019, at 09:39, Christopher Faulet wrote: > > Le 28/10/2019 à 22:00, Christopher Faulet a écrit : >>> macbookpro:~ andreavettori$ curl --http2 -v http://g.testhost >> [SNIP] >> Here, it is the expected behavior. HAProxy does not support explicit H2 >> upgrade. > > In Fact, for this

Re: Truncated response on 2.0.8

Le 28/10/2019 à 22:00, Christopher Faulet a écrit : macbookpro:~ andreavettori$ curl --http2 -v http://g.testhost [SNIP] Here, it is the expected behavior. HAProxy does not support explicit H2 upgrade. In Fact, for this one, I was wrong. The result should be more or less the same that an

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

Le 28/10/2019 à 15:49, Ing. Andrea Vettori a écrit : If it is on a development platform, is there any way to have a full network capture ? Thanks for your help. The server where haproxy is running is a production server while this specific front/backend is a development web site. I can

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. >> I’ve tried to use http2 on the

Re: Truncated response on 2.0.8

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. I’ve tried to use http2 on the development backend but I get truncated response (not always but very

Re: Truncated response on 2.0.8

On 2019-10-26 18:10, Ing. Andrea Vettori wrote: 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. I’ve tried to use http2 on the development backend but I get truncated response (not always but very often).