Subj : Re: synchronet behind a reverse proxy
To : martylake
From : echicken
Date : Thu Nov 25 2021 20:53:34
Re: Re: synchronet behind a reverse proxy
By: martylake to echicken on Thu Nov 25 2021 12:21:45
ma> at the moment don't need the `check-proxy v2` option for the magic header
ma> x-forwarded-for to happen. Instead it just needs the option
ma> `forwarder-for`. As far as I understand too yes, I just discovered this
ma> mode two days ago.
If you want to check if this is really happening, you can put this file somewhere on your Synchronet webserver as 'headers.xjs', then browse to it and see what it spits out:
Headers
Object.keys(http_request.header).forEach(function (e) { ?>
write(e); ?>: write(http_request.header[e]); ?>
}); ?>
One of the rows should show the x-forwarded-for header.
ma> I just compiled synchronet locally, but if I run it, it complains about
ma> missing configuration files. I should RTFM to figure out how to properly
ma> do it.
ma> I guess I will be able to pull changes that you push on a branch.
Sorry, I should have asked if you did a development / git-based installation in the first place. Once you have one working, let me know. I'll tinker with this a bit tonight if I'm able, or tomorrow.
---
echicken
electronic chicken bbs - bbs.electronicchicken.com
---
þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
.