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

**URL:** <https://discourse.haproxy.org/t/http-in-2-in-log-what-does-it-mean/9251>\
**Category:** Help!\
**Created:** [November 21, 2023, 11:18am UTC](https://discourse.haproxy.org/t/http-in-2-in-log-what-does-it-mean/9251 "2023-11-21T11:18:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![chriskuku](https://avatars.discourse-cdn.com/v4/letter/c/7feea3/32.png) [@chriskuku](https://discourse.haproxy.org/u/chriskuku)\
**Post date:** [November 21, 2023, 11:18am UTC](https://discourse.haproxy.org/t/http-in-2-in-log-what-does-it-mean/9251/1 "2023-11-21T11:18:32Z")

</div>

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 ->`](https://discourse.haproxy.org/t/sl-handshake-failure-errorssl-routines-callback-failed/9248) , which is still unanswered),  
I’m wondering what `http-in/2`means in my `haproxy.log`.

My guess: second bind address?

```auto
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

```

---

<div class="post-metadata">

**Author:** ![ToddColeman](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.haproxy.org/toddcoleman/32/2383_2.png) [@ToddColeman](https://discourse.haproxy.org/u/ToddColeman)\
**Post date:** [January 3, 2025, 4:23pm UTC](https://discourse.haproxy.org/t/http-in-2-in-log-what-does-it-mean/9251/2 "2025-01-03T16:23:16Z")

</div>

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.