While experimenting with enabling QUIC in HAProxy sitting in front of our closed-source application I stumbled upon a reproducible QUIC protocol failure/malfunction while accessing specific CSS resource, which is served via internal application proxy: accessing it over QUIC results either in ERR_QUIC_PROTOCOL_FAILURE in the browser and no mention of request in HAProxy log or incomplete resource being download and CD-- request termination flags in HAProxy log (and logged request looks a bit different from other, successful, H3 requests). Accessing the same resource over HTTP/2 works fine. I need help with setting up a proper debug session so that I could capture all necessary information which may help with fixing this issue: HAProxy internal debugging/tracing flags to enable, etc. I don't want to open a bug on GitHub for this and would appreciate if anyone from HAProxy team could reach out to me directly so that I could share relevant information and attempt to debug under your direction.
Thanks in advance, Vladimir "Bob" Zakharychev
