On 4/12/22 14:07, Frederic Lecaille wrote:
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.
These are the trace commands that I am sending to the stats socket:
trace quic sink buf0; trace quic level developer; trace quic verbosity
clean; trace quic start now
trace qmux sink buf0; trace qmux level developer; trace qmux verbosity
minimal; trace qmux start now
trace stream sink buf0; trace stream level developer; trace stream
verbosity clean; trace stream start now
I am sure that I have pressed enter after the last line. If I have
copied that third line correctly, then nothing is being logged for stream.
The "index.php" file is not equipped to deal with a POST request, but
apache doesn't log anything, so I don't think it's ever getting to PHP.
It correctly executes the script when using http2.
The script just checks a header that I am setting in haproxy, to say
"YES" or "NO" depending on whether the browser was doing http3.
https://http3test.elyograg.org/
If you load the page in Firefox, you need to do a regular page reload to
get it doing http3. In Chrome, it needs to be a shift-reload. If you
do vice-versa, it will never switch to http3. I wonder which behavior
could be considered a bug.
I expect that there is probably no set release data for 2.6.0, but is
there a ballpark date when it MIGHT be ready for release?
Thanks,
Shawn
