Http-in/2 in log - what does it mean?

While I’m trying to tackle what happens with a not functioning ssl- handshake
on a connection (see other of my posts on this topic -> , which is still unanswered),
I’m wondering what http-in/2means in my haproxy.log.

My guess: second bind address?

frontend http-in
    bind *:80
    bind *:443 ssl crt /etc/haproxy/certs/ strict-sni
    bind quic4@0.0.0.0:443 name quic443 ssl crt /etc/haproxy/certs/www.mydomain.org.pem proto quic alpn h3,h3-29,h3-28,h3-27 npn h3,h3-29,h3-28,h3-27 allow-0rtt curves secp521r1:secp384r1

The /2 means that it’s the second bind definition. If you were to swap the order of the first two bind definitions, putting 443 first and port 80 second, you’d start seeing those messages come in as http-in/1.