Hi Dave.
On 2024-06-12 (Mi.) 12:45, Aleksandar Lazic wrote:
On 2024-06-12 (Mi.) 12:26, Dave Cottlehuber wrote:
On Tue, 11 Jun 2024, at 22:57, Aleksandar Lazic wrote:
Hi Dave.
Thank you for your test and feedback.
When you put this line into backend, will this be better?
```
tcp-request connection upstream-proxy-header HOST www.httpbun.com
```
Regards
Alex
Hi Alex,
Sorry I forgot to mention that. This is not allowed by the backend:
[ALERT] (76213) : config : parsing
[/usr/local/etc/haproxy/haproxy.conf:228] : tcp-request connection is not
allowed because backend stream_be is not a frontend
So there is likely a simple solution to allow these in either end.
Not yet, afaik.
Looks like the "tcp-request content ..." is the solution.
```
frontend stream_fe
bind :::8443 v4v6
mode tcp
option tcplog
default_backend stream_be
backend stream_be
mode tcp
log global
tcp-request content upstream-proxy-header HOST www.httpbun.com
tcp-request content set-dst-port int(4433)
#tcp-request content set-hostname %[str(www.test1.com)]
tcp-request content upstream-proxy-header Host www.test1.com
tcp-request content upstream-proxy-header Proxy-Authorization "basic
%[env(MYPASS),base64]"
#server stream www.httpbun.com:443 upstream-proxy-tunnel 123.45.67.89:8000
server https_Via_Proxy1 www.test1.com:4433 upstream-proxy-tunnel
127.0.0.1:3128 init-addr 127.0.0.1
```
Looks like there is still a lot of work to do.
I work on that, stay tuned for updates.
From my point of view are the *upstream-proxy* settings only useful in the
backend section.
A+
Dave
Regards
Alex
