How to test quic on version 2.5

How to test the Haproxy http3 protocol, I have successfully compiled haproxy 2.5 and 2.6-dev1 through quictls/openssl, but found that I will not configure the use of quic, and there is no UDP port development for background port monitoring.

COMMAND   PID    USER   FD   TYPE   DEVICE SIZE/OFF NODE NAME
haproxy 12409 haproxy    3u  IPv4 15459889      0t0  TCP *:https (LISTEN)
haproxy 12409 haproxy    5u  IPv4 15459891      0t0  TCP *:https (LISTEN)
global
	log /dev/log local0
	log /dev/log local1 notice
	chroot /var/lib/haproxy
	user haproxy
	group haproxy
	daemon

defaults
	log global
	option tcplog
	option dontlognull
	timeout connect 10s
	timeout client 30s
	timeout server 30s

frontend ft_main
	mode http
	bind *:443 ssl crt /etc/haproxy/certs/

	default_backend exp1.com

backend exp1.com
	mode http
	server s1 127.0.0.1:8000
HAProxy version 2.5.0 2021/11/23 - https://haproxy.org/
Status: stable branch - will stop receiving fixes around Q1 2023.
Known bugs: http://www.haproxy.org/bugs/bugs-2.5.0.html
Running on: Linux 4.14.129-bbrplus #1 SMP Mon Jun 24 16:51:05 UTC 2019 x86_64
Build options :
  TARGET  = generic
  CPU     = generic
  CC      = cc
  CFLAGS  = -O2 -g -Wall -Wextra -Wundef -Wdeclaration-after-statement -fwrapv -Wno-unused-label -Wno-sign-compare -Wno-unused-parameter -Wno-clobbered -Wno-missing-field-initializers -Wtype-limits -Wshift-negative-value -Wshift-overflow=2 -Wduplicated-cond -Wnull-dereference
  OPTIONS = USE_STATIC_PCRE=1 USE_OPENSSL=1 USE_ZLIB=1 USE_QUIC=1
  DEBUG   = 

Feature list : -EPOLL -KQUEUE -NETFILTER -PCRE -PCRE_JIT -PCRE2 -PCRE2_JIT +POLL -THREAD -BACKTRACE +STATIC_PCRE -STATIC_PCRE2 +TPROXY -LINUX_TPROXY -LINUX_SPLICE -LIBCRYPT -CRYPT_H -GETADDRINFO +OPENSSL -LUA -ACCEPT4 -CLOSEFROM +ZLIB -SLZ -CPU_AFFINITY -TFO -NS -DL -RT -DEVICEATLAS -51DEGREES -WURFL -SYSTEMD -OBSOLETE_LINKER -PRCTL -PROCCTL -THREAD_DUMP -EVPORTS -OT +QUIC -PROMEX -MEMORY_PROFILING

Default settings :
  bufsize = 16384, maxrewrite = 1024, maxpollevents = 200

Built with OpenSSL version : OpenSSL 3.0.1+quic 14 Dec 2021
Running on OpenSSL version : OpenSSL 3.0.1+quic 14 Dec 2021
OpenSSL library supports TLS extensions : yes
OpenSSL library supports SNI : yes
OpenSSL library supports : TLSv1.0 TLSv1.1 TLSv1.2 TLSv1.3
Built with zlib version : 1.2.8
Running on zlib version : 1.2.8
Compression algorithms supported : identity("identity"), deflate("deflate"), raw-deflate("deflate"), gzip("gzip")
Built without multi-threading support (USE_THREAD not set).
Support for malloc_trim() is enabled.
Built with transparent proxy support using: IP_TRANSPARENT IP_FREEBIND
Built with PCRE version : 8.39 2016-06-14
Running on PCRE version : 8.39 2016-06-14
PCRE library supports JIT : no (USE_PCRE_JIT not set)
Encrypted password support via crypt(3): no
Built with gcc compiler version 6.3.0 20170516

Available polling systems :
       poll : pref=200,  test result OK
     select : pref=150,  test result OK
Total: 2 (2 usable), will use poll.

Available multiplexer protocols :
(protocols marked as <default> cannot be specified using 'proto' keyword)
            quic : mode=HTTP       side=FE|BE     mux=QUIC     flags=HTX|CLEAN_ABRT|HOL_RISK
              h2 : mode=HTTP       side=FE|BE     mux=H2       flags=HTX|CLEAN_ABRT|HOL_RISK|NO_UPG
            fcgi : mode=HTTP       side=BE        mux=FCGI     flags=HTX|HOL_RISK|NO_UPG
       <default> : mode=HTTP       side=FE|BE     mux=H1       flags=HTX
              h1 : mode=HTTP       side=FE|BE     mux=H1       flags=HTX|NO_UPG
       <default> : mode=TCP        side=FE|BE     mux=PASS     flags=
            none : mode=TCP        side=FE|BE     mux=PASS     flags=NO_UPG

Available services : none

Available filters :
	[SPOE] spoe
	[CACHE] cache
	[FCGI] fcgi-app
	[COMP] compression
	[TRACE] trace

I seem to see examples of successful images on twitter, but I don’t know how to configure it, I’d love to know what’s inside test-quic.cfg https://twitter.com/hashtag/HAProxy?src=hashtag_click

QUIC is in development, highly experimental and undocumented, I suggest you use the mailing list to discuss development. However don’t expect generic support. Filing bugs on github is also not the correct way, we use this for feature request and bug reports only.