# Gather more info about TLS Client Hello messages being received on port 80

**URL:** https://discourse.haproxy.org/t/gather-more-info-about-tls-client-hello-messages-being-received-on-port-80/3229
**Category:** Help!
**Created:** [November 15, 2018, 3:34pm UTC](https://discourse.haproxy.org/t/gather-more-info-about-tls-client-hello-messages-being-received-on-port-80/3229 "2018-11-15T15:34:50Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![lukastribus](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lukastribus](https://discourse.haproxy.org/u/lukastribus)
#### Post date: [November 15, 2018, 4:11pm UTC](https://discourse.haproxy.org/t/gather-more-info-about-tls-client-hello-messages-being-received-on-port-80/3229/4 "2018-11-15T16:11:12Z")

</div>

Sure, that’s what I suggested in the last thread:

> [@Invalid requests](https://discourse.haproxy.org/t/invalid-requests/3098/10):
>
> Yes, but it requires an additional frontend/backend layer to distinguish between HTTP and HTTPS. Take a look at this thread:

Read the thread about content switching between HTTP and SSL on a single port and then you can decode it in haproxy and log everything you like.

---

_[View the full topic](https://discourse.haproxy.org/t/gather-more-info-about-tls-client-hello-messages-being-received-on-port-80/3229)._