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
PROXY protocol can be useful to preserve the client IP address when a
non-transparent load balancer is used. PROXY protocol v1 is human
readable while v2 is binary.
github.com/armon/go-proxyproto supports only PROXY protocol v1.
github.com/pires/go-proxyproto supports PROXY protocol v1 & v2.
Some load balancers support PROXY protocol v1, e.g. AWS classic load
balancer. Others only support PROXY protocol v2, e.g. AWS network load
balancer.
If the previous implementation received PROXY protocl v2 it did not
detect it and forwarded it as workload data. In conjunction with TLS
this lead to a packet including PROXY protocol v2 AND the TLS client
hello being forwarded to nginx causing issues (400 Bad Request).
With the new library, it is possible to run ingress-nginx with ssl
passthrough and PROXY protocol enabled in environments using PROXY
protocol v2.
0 commit comments