> Could you share your configuration please ? If it only happens on a specific > endpoint, you can remove configuration of the others. Then if it is easily > reproducible, you may try to find the minimal config to do so. Finally a > network capture on a server side may help too (share it privately). > > In the mean time, could you describe your request and your response when the > problem occurs (size, chunked-encoding Vs content-length, compression ...) ? > And from the browser point of view, is there any difference with and without > the HTX ? > > If possible, could you try disabling the h2 on the frontend side ? It could > help to identify where the problem is. > > Finally, have you already tested other 2.X versions without encountering the > problem?
This was resolved outside of the mailing list. The root cause had to do with the message length and handling of the HTX EOM block in a full HTX buffer in mux-h1. Commit 7aae858001f99dd4a80e3f533284cda5702d501a in the public development tree resolves the issue. Backported as 6f6886e021828a24295271bd83b33a9917d70323 for haproxy-2.1 and a882a46eefc4b2beeae2fc552e375bd0ff63f072 for haproxy-2.0 trees, expectedly shipping as v2.1.1 and v2.0.11 respectively. Big thank you to Christopher for the work done! Best regards, Valters Jansons
