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
If you have use_proxy_proto in your ambassador module, but you don't have any TLS termination contexts, we don't actually set use_proxy_proto in the Envoy config in 0.50.0-rc1 (and likely not in -ea7 either, as it appears that the bug was introduced with SNI support).
The fix is probably just to make sure that the base filter chains in v2listener.py, even without SNI, properly set use_proxy_proto. We also need to better test this (obviously).
The text was updated successfully, but these errors were encountered:
If you have
use_proxy_proto
in yourambassador
module, but you don't have any TLS termination contexts, we don't actually setuse_proxy_proto
in the Envoy config in 0.50.0-rc1 (and likely not in -ea7 either, as it appears that the bug was introduced with SNI support).The fix is probably just to make sure that the base filter chains in
v2listener.py
, even without SNI, properly setuse_proxy_proto
. We also need to better test this (obviously).The text was updated successfully, but these errors were encountered: