# Invalid requests

**URL:** https://discourse.haproxy.org/t/invalid-requests/3098
**Category:** Help!
**Created:** [October 15, 2018, 8:50pm UTC](https://discourse.haproxy.org/t/invalid-requests/3098 "2018-10-15T20:50:30Z")
**Posts on this page:** 1
**Showing post:** 10

<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: [October 30, 2018, 11:35am UTC](https://discourse.haproxy.org/t/invalid-requests/3098/10 "2018-10-30T11:35:24Z")

</div>

Yes, but it requires an additional frontend/backend layer to distinguish between HTTP and HTTPS. Take a look at this thread:

> [@TLS Termination Proxy with both TLS and plain TCP on the same port](https://discourse.haproxy.org/t/tls-termination-proxy-with-both-tls-and-plain-tcp-on-the-same-port/2885/):
>
> We’re considering using HAProxy as a TLS termination proxy, running in front of our TCP server where our clients connect with their front-end apps. I’m wondering if HAProxy is capabale of making distinction between SSL connection and plain connection on the same port in the frontend section (like binding for example on port 80 both the plain and the ssl sockets), and regardless if it’s an encrypted or non-encrypted connection, it will be proxied on to the backend server: if it’s a plain connect…

---

_[View the full topic](https://discourse.haproxy.org/t/invalid-requests/3098)._