Subj : Re: synchronet behind a reverse proxy
To   : echicken
From : martylake
Date : Thu Nov 25 2021 20:19:04

  Re: Re: synchronet behind a reverse proxy
  By: echicken to martylake on Fri Nov 26 2021 04:08 am

Dear echicken,

 > Is HAProxy reverse-proxying websocket connections to Synchronet's websocket
 > service? This needs to be configured in addition to reverse proxying traffic
 > to Synchronet's webserver. (Hint: you probably had to set values for 'wsp'
 > and 'wssp' in the [web] section of 'ctrl/modopts.ini' if you set this up.)

Yes it currently is, it looks like this:
The_Internet -> ISP's router -> haproxy -> wss port of sbbs -> telnet sbbs

If I disable sbbs' HAPROXY_PROTO, the web telnet wrapper works great.

 > You mentioned something in an earlier message about HAProxy lowercasing the
 > names of HTTP headers. If the client sends 'Some-Header: Some Data', can I
 > expect the upstream to receive 'some-header: Some Data'? This will become
 > important, because it looks like the websocket service currently does
 > case-sensitive matching on header lines.

There are a couple of settings in haproxy to massage the headers so they arrive in the expected capitalization.

By default, haproxy would lowercase all headers, the way you described in your example `Some-Header: Some Data` -> haproxy -> `some-header: Some Data`. If it's not too much trouble, changing from case-sensitive matching to case-insensitive matching for headers would make the websocket service more compatible, but it is not mandatory at all, as I said, haproxy also has options to specify the required header capitalization per route.

When I get this whole setup working, I can suggest a few edits to synchronet's  wiki's proxy page to account for all those peculiarities.
--- SBBSecho 3.14-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.