Hi Tim,

On Fri, 24 May 2019 at 13:36, Tim Düsterhus <[email protected]> wrote:
>
> Lukas,
>
> Am 24.05.19 um 11:27 schrieb Lukas Tribus:
> > FYI this was double posted and has already been looked at here:
> >
> > https://discourse.haproxy.org/t/chained-haproxy-in-tcp-mode-with-proxy-protocol-enabled-not-working/3843/
> >
>
> I'm not signed up in Discourse, thus here on the list.
>
> I believe when `accept-proxy` is configured on HAProxy B there should be
> another `send-proxy` in the `server` line of HAProxy B, no?

Correct, 'accept-proxy' on haproxy B is a wrong and irrelevant
configuration, it was wrongly used for testing purposes (and confirms
that the backend server expects plain SSL instead of PROXY+SSL).

The point is that unless the source IP is needed on haproxy B, the
PROXY protocol can be passed transparently to the backend server,
without accepting and rewriting it on the backend.

Lukas

Reply via email to