haproxy returns 200 instead of 101 for websockets - from 2.7 forward

planetinse · Feb 20, 2024, 1:00 PM

This (seems) to introduce some interesting caching issues, where I get connected to the wrong backend (when switching urls it reuses the previous websocket)
luckily customers are 1:1 to their fqdn, but from a testing perspective this is annoying as hell, and i really dont want to go back to older versions of pfsense/haproxy.
I'll be happy to pay someone just to have a speaking partner on this....

planetinse · Feb 20, 2024, 4:16 PM

@planetinse

23.09.1
I have taken away all other logic and just trying to offload TLS, (no fiddle with sni_fc_ssl or likewise) - and instead of expected 101 and Upgrade response header, I get 200, the tunnel is created and it works, but browser reuses earlier tunnel if i switch url that should use another backend. (it gets confused by the 200 response is my theory)

2.4
doing the same thing with the in 2.4 i get Expected 101 and Upgrade response header.

Direct
If i access backend directly it gives me the expected 101 and Connection upgrade.