Hello Shawn, On 4/12/22 18:30, Shawn Heisey wrote: > On 4/12/22 09:45, Amaury Denoyelle wrote: >> After much analysis of the code, it may be useful to have a run with the >> stream traces as well : >> $ trace stream sink buf0; trace stream level developer; trace stream >> verbosity clean; trace stream start now > > All 3 traces enabled, this time it should only be for one connection, I > think the last one there were two:
It's ok for the quic and qmux parts. But I do not seen any trace for the stream part. You should see such a traces when your h3 client open a stream (truncated here, without timestamp). Note the second field of the traces: "quic", "qmux", "stream" [04|quic|2|t_quic.c:2543] RX frame : qc@0x7f56cc3c08e0 STREAM_A uni=1 fin=0 id=10 off=0 len=1 [04|qmux|5|ux_quic.c:101] qcs_new(): entering : qcc=0x7f56cc376e60(F) [04|qmux|5|ux_quic.c:144] qcs_new(): leaving : qcc=0x7f56cc376e60(F) qcs=0x7f56cc35cf20(6) [04|qmux|5|ux_quic.c:101] qcs_new(): entering : qcc=0x7f56cc376e60(F) [04|qmux|5|ux_quic.c:144] qcs_new(): leaving : qcc=0x7f56cc376e60(F) qcs=0x7f56cc35af20(10) . . . [04|stream|5|/stream.c:348] stream_new(): entering [04|stream|5|/stream.c:566] stream_new(): leaving : [2,HTX] SI=(EST,INI) . . . Please, you could you double check on your side the "stream" traces are correctly enabled? Also ensure you provide use with traces dumped by haproxy when you validate the PHP form. Thank you.
