At first, I was using HTTPS only. But this prevents reading the data in tcpdump. But using HTTPS or HTTP doesn't change anything on w3m behaviour.
On Tue, Mar 04, 2025 at 07:00:03AM GMT, Dan wrote: > Hello.. > First about your prb, just want to hint you about the syntax of relayd.conf > what could be a missmatch > between port 80 and SSL. Did you try to play around that? > Second really thx to pop up with this software.. > > Dan > > ------ > bsdload.com - Repo: https://code.5mode.com > > Please reply to the mailing-list, leveraging technical stuff. > > Mar 4, 2025 00:46:46 Joel Carnat <j...@carnat.net>: > > > I've stripped down relayd.conf as much as possible and it looks like > > this: > > ======================================================================== > > wan_ipv4 = "192.168.0.64" > > localhost = "127.0.0.1" > > sx_port = "8888" > > > > interval 5 > > > > log state changes > > log connection errors > > log connection > > > > table <searxng> { $localhost } > > > > http protocol www { > > match request header set "X-Forwarded-For" value "$REMOTE_ADDR" > > match request header set "X-Real-IP" value "$REMOTE_ADDR" > > match request header set "X-Scheme" value "https" > > match request header set "X-Script-Name" value "/searxng" > > } > > > > relay www { > > listen on $wan_ipv4 port 80 > > protocol www > > forward to <searxng> port $sx_port > > } > > ======================================================================== > > > > Is there a way to correct this and have w3m work? > > > > Thanks for help, > > Joel C. >
