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
The mesh gateway envoy proxy has the default value of false for use_remote_address in the HTTP connection manager config.
The documentation makes it clear that this should be set to true when the downstream is untrusted:
and
This affects how headers such as x-forwarded-for and x-forwarded-proto are treated.
For example, despite the fact that the connection with the downstream is TLS, our mesh gateway redirects the client because the x-forwarded-proto is (incorrectly) set to http by the client and we have require_tls set to all.
The text was updated successfully, but these errors were encountered:
What happened?
The mesh gateway envoy proxy has the default value of
false
foruse_remote_address
in the HTTP connection manager config.The documentation makes it clear that this should be set to
true
when the downstream is untrusted:and
This affects how headers such as
x-forwarded-for
andx-forwarded-proto
are treated.For example, despite the fact that the connection with the downstream is TLS, our mesh gateway redirects the client because the
x-forwarded-proto
is (incorrectly) set tohttp
by the client and we haverequire_tls
set toall
.The text was updated successfully, but these errors were encountered: