Subj : Re: synchronet behind a reverse proxy
To   : echicken
From : deon
Date : Fri Nov 26 2021 10:41:23

  Re: Re: synchronet behind a reverse proxy
  By: echicken to martylake on Thu Nov 25 2021 07:25 pm

 > Assuming it's acting as a typical HTTP reverse proxy where it interacts with the Synchronet web and websocket services, it should be sending the 'x-forwarded-for' header along to the upstream. If so, we would need to make the websocket server:
 >
 > 1) Capture the value of the x-forwarded-for header
 > 2) Check if the telnet server has the HAPROXY_PROTO flag in sbbs.ini
 > 3) Speak the HAProxy protocol when connecting to the telnet server
 >
 > Parts 1 & 2 are simple. A glance at HAProxy's docs suggest that 3 is no big deal either, but I may be missing something.

Yup, that will do it.

3) is easy - you should be able to talk the v1 or v2 protocol, there is a link to it in the comments of the source code. Its basically the first string of chars when the connection is made, before doing actual telnet stuff.



....лоеп

---
 ю Synchronet ю Alterant | an SBBS in Docker on Pi!
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.