Subj : Re: synchronet behind a reverse proxy
To   : deon
From : martylake
Date : Thu Nov 25 2021 22:12:53

  Re: Re: synchronet behind a reverse proxy
  By: deon to martylake on Fri Nov 26 2021 04:22 pm

Dear deon,

 > browser -> haproxy (http port) -> websocket -> haproxy (telnet port) -> sbbs
 > (telnet port)
 > Looks like echicken was working on the last item - I would have thought for
 > the first one, you can change "localhost:23" to "haproxy:23"?

I misunderstood, indeed ! I think proposition 2 it equivalent to proposition 3 because if websocket does not forward haproxy instructions, there is no way to retrieve back this information down the chain:

browser -> haproxy (http port, adds http header x-forwarded-from) -> websocket (currently discards information) -> ...whatever comes after does not have the information anymore ?

I hope contributing as guinea pig for echicken helps. The spec of proxy_protool does not look so long, but I have never implemented such network specs before so Iÿam not sure if my intuition is correct there.
--- SBBSecho 3.14-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.