Get desktop application:
View/edit binary Protocol Buffers messages
Configuration for the dynamic forward proxy HTTP filter. See the :ref:`architecture overview <arch_overview_http_dynamic_forward_proxy>` for more information. [#extension: envoy.filters.http.dynamic_forward_proxy]
The DNS cache configuration that the filter will attach to. Note this configuration must match that of associated :ref:`dynamic forward proxy cluster configuration <envoy_v3_api_field_extensions.clusters.dynamic_forward_proxy.v3.ClusterConfig.dns_cache_config>`.
The configuration that the filter will use, when the related dynamic forward proxy cluster enabled sub clusters.
When this flag is set, the filter will add the resolved upstream address in the filter state. The state should be saved with key ``envoy.stream.upstream_address`` (See :repo:`upstream_address.h<source/common/stream_info/upstream_address.h>`).
Per route Configuration for the dynamic forward proxy HTTP filter.
Indicates that before DNS lookup, the host header will be swapped with this value. If not set or empty, the original host header value will be used and no rewrite will happen. Note: this rewrite affects both DNS lookup and host header forwarding. However, this option shouldn't be used with :ref:`HCM host rewrite <envoy_v3_api_field_config.route.v3.RouteAction.host_rewrite_literal>` given that the value set here would be used for DNS lookups whereas the value set in the HCM would be used for host header forwarding which is not the desired outcome.
Indicates that before DNS lookup, the host header will be swapped with the value of this header. If not set or empty, the original host header value will be used and no rewrite will happen. Note: this rewrite affects both DNS lookup and host header forwarding. However, this option shouldn't be used with :ref:`HCM host rewrite header <envoy_v3_api_field_config.route.v3.RouteAction.auto_host_rewrite>` given that the value set here would be used for DNS lookups whereas the value set in the HCM would be used for host header forwarding which is not the desired outcome. .. note:: If the header appears multiple times only the first value is used.
Used in:
The timeout used for sub cluster initialization. Defaults to 5s if not set.