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
Ambassador 1.0.0+ does not appear to properly handle the proxy protocol when terminating tls.
To reproduce:
Deploy aes
set use_proxy_proto: true in a Module
Exec into the ambassador container and send a curl to an endpoint with --haproxy-protocol flag (this is easier than needing to configure a load balancer that enables the proxy protocol)
Get an SSL error:
$ curl -vk https://localhost:8443/ambassador/v0/diag/
* Trying 127.0.0.1:8443...
* TCP_NODELAY set
* Connected to localhost (127.0.0.1) port 8443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to localhost:8443
* Closing connection 0
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to localhost:8443
Ambassador 1.0.0+ does not appear to properly handle the proxy protocol when terminating tls.
To reproduce:
Deploy aes
set
use_proxy_proto: true
in aModule
Exec into the ambassador container and send a curl to an endpoint with
--haproxy-protocol
flag (this is easier than needing to configure a load balancer that enables the proxy protocol)Get an SSL error:
A look at the
envoy.json
seems correct:This behavior is not in 86.1 and lower:
envoy.json
The text was updated successfully, but these errors were encountered: