On 11/25/21 16:38, deon wrote:
 >>> So reconfigure the websockets part to connect to haproxy's port,
 >>> not SBBS directly.
 >>
 >> The issue is that websocket is a protocol on top of http, that's
 >> why we need a websocket->telnet proxy. The issue if I understand
 >> correctly is that this proxy is not forwarding haproxy information
 >> to the backend.
 >
 > Correct, there are two paths that could address this.
 >
 > * The websocket connects to haproxy, not SBBS directly.
 >
 > * The websocket speaks that haproxy protocol when talking with
 > SBBS directly.
 >
 > The first is probably easy to do, if you can configure it via a
 > config file (sorry I dont know).
 >
 > The second would require development I'm guessing...

The haproxy websocket connection should forward the given path(s) to the 
websocket port on synchronet as a tcp connection... or upcycle... I 
don't know if haproxy supports acting as a websockettcp gateway directly.

I've tried to make a specific path or websocket connection upgrade work 
to reverse-proxy to a different port, but it doesn't want to work 
correctly... kind of wish that websocket connection 
support/configuration was directly in the sbbs http service itself, 
which would make that part much easier to work with.
-- 
Michael J. Ryan - tracker1@roughneckbbs.com
---
 þ Synchronet þ Roughneck BBS - roughneckbbs.com
--- SBBSecho 3.14-Linux