Hacker News Reader

The extra setup step for websocket should not be required: https://caddyserver.com/docs/v2-upgrade#proxy

I also had no problems with HAProxy, it worked with websockets without any issues or extra handling.

That's correct, just `reverse_proxy` alone is enough. The request matcher is only needed if you want to make the same request paths get proxied to your HTTP upstream if it doesn't have those websocket connection headers. But if you're always using a path like `/ws` for websockets then you don't need to match on headers.

Reply on news.ycombinator.com