You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can sniproxy be behind another SNI proxy (maybe another sniproxy) which has enabled the proxy_protocol feature? Is sniproxy able to receive proxy_protocol connections?
I am testing with a sniproxy behind another sniproxy. It looks like this:
---> sniproxy1 ---> sniproxy2 ---> backend
I have enabled proxy_protocol on sniproxy2 and on backend and this works fine.
But when I try to enable proxy_protocol on sniproxy1, things break.
This seems reasonable to me because I expect that sniproxy2 needs to be configured so that it is able to receive proxy_protocol connections (instead of plain HTTPS). However I am not able to find any setting for this on the man page.
I guess that it should be a setting of listener, and it should look like this: protocol proxy_tls. However the only protocols supported (according to the man page) are protocol http and protocol tls.
Am I missing something?
The text was updated successfully, but these errors were encountered:
Can
sniproxy
be behind another SNI proxy (maybe anothersniproxy
) which has enabled the proxy_protocol feature? Issniproxy
able to receive proxy_protocol connections?I am testing with a
sniproxy
behind anothersniproxy
. It looks like this:I have enabled proxy_protocol on
sniproxy2
and onbackend
and this works fine.But when I try to enable proxy_protocol on
sniproxy1
, things break.This seems reasonable to me because I expect that
sniproxy2
needs to be configured so that it is able to receive proxy_protocol connections (instead of plain HTTPS). However I am not able to find any setting for this on the man page.I guess that it should be a setting of
listener
, and it should look like this:protocol proxy_tls
. However the only protocols supported (according to the man page) areprotocol http
andprotocol tls
.Am I missing something?
The text was updated successfully, but these errors were encountered: