Hi Christopher, First : good news : I was not able to reproduce the issue with 2.1-dev2-e0f48a-88 and HTX enable. I guess e0f8dc576f62ace9ad1055ca068ab5d4f3a952aa was the culprit.
To answer your questions and for others on the list : - The issue arose with H1 (H2 not enable) - It's the client who complained about a malformed payload thus it was unable to unmarshall datas into a valid object (it was the result of an API call). The message from the client is a short error message like "expecting [0-9a-fA-F] but got 0x4f" (note that 0x4f is not a constant and would vary from run to run) - To my understanding, the payload is chunk-encoded. -- Ionel GARDAIS Tech'Advantage CIO - IT Team manager ----- Mail original ----- De: "Christopher Faulet" <[email protected]> À: "Ionel GARDAIS" <[email protected]>, "Willy Tarreau" <[email protected]> Cc: "haproxy" <[email protected]> Envoyé: Mardi 15 Octobre 2019 10:20:50 Objet: Re: Issue with HTX Le 12/10/2019 à 14:23, GARDAIS Ionel a écrit : > I might have been too enthusiast. > haproxy is set as a TLS-endpoint thus the traces from the client-side are > encrypted. > The trace of the server side is plain text but as this is the client which > complains about a malformed packet, client-side should be compared to > server-side. > > Instead of a tcpdump, I should run full debug on haproxy. > Could you tell me how to do this for HTX ? > > Also, as I was looking at the traces, note that protobuf is involved in the > client-server exchange. > It might change how debug and traces are collected. > Hi, The data corruption happens for H1 or H2 connections (or both) ? On the client side or the server side ? If it is related to H1 connections, is the payload chunk-encoded or not ? If yes, I pushed a fix yesterday that may help. If so, give the last 2.1 snapshot a try. Then, which kind of data corruption did you observe and how did you observe it ? Finally, could you share your configuration please ? Thanks, -- Christopher Faulet -- 232 avenue Napoleon BONAPARTE 92500 RUEIL MALMAISON Capital EUR 219 300,00 - RCS Nanterre B 408 832 301 - TVA FR 09 408 832 301
