From ebb3e787d2dcf01a2e9de57ab3eeb7b1131eaffb Mon Sep 17 00:00:00 2001 From: "update-envoy[bot]" <135279899+update-envoy[bot]@users.noreply.github.com> Date: Thu, 1 Feb 2024 19:35:20 +0000 Subject: [PATCH] chore: remove `append_x_forwarded_host_idempotent` runtime flag (#32102) chore: remove `append_x_forwarded_host` runtime flag Signed-off-by: River Phillips Mirrored from https://github.com/envoyproxy/envoy @ 6762bf3e17512bdb3b49c748dc75dd2000494606 --- envoy/config/route/v3/route_components.proto | 1 - 1 file changed, 1 deletion(-) diff --git a/envoy/config/route/v3/route_components.proto b/envoy/config/route/v3/route_components.proto index 1e2b486d..3e755301 100644 --- a/envoy/config/route/v3/route_components.proto +++ b/envoy/config/route/v3/route_components.proto @@ -1211,7 +1211,6 @@ message RouteAction { // :ref:`host_rewrite_path_regex `) // causes the original value of the host header, if any, to be appended to the // :ref:`config_http_conn_man_headers_x-forwarded-host` HTTP header if it is different to the last value appended. - // This can be disabled by setting the runtime guard ``envoy_reloadable_features_append_xfh_idempotent`` to false. bool append_x_forwarded_host = 38; // Specifies the upstream timeout for the route. If not specified, the default is 15s. This