Dynamic forward proxy

    As of Envoy v1.18 the v2 API has been removed and is no longer supported.

    If you are upgrading from v2 API config you may wish to view the v2 API documentation:

    [extensions.filters.http.dynamic_forward_proxy.v3.FilterConfig proto]

    Configuration for the dynamic forward proxy HTTP filter. See the for more information.

    This extension may be referenced by the qualified name

    Note

    This extension is intended to be robust against untrusted downstream traffic. It assumes that the upstream is trusted.

    This extension extends and can be used with the following extension category:

    dns_cache_config

    (, REQUIRED) The DNS cache configuration that the filter will attach to. Note this configuration must match that of associated dynamic forward proxy cluster configuration.

    save_upstream_address

    () 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 upstream_address.h).

    extensions.filters.http.dynamic_forward_proxy.v3.PerRouteConfig

    [extensions.filters.http.dynamic_forward_proxy.v3.PerRouteConfig proto]

    Per route Configuration for the dynamic forward proxy HTTP filter.

    host_rewrite_literal

    Note: this rewrite affects both DNS lookup and host header forwarding. However, this option shouldn’t be used with 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.

    Only one of host_rewrite_literal, may be set.

    host_rewrite_header

    (string) 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 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.

    Only one of host_rewrite_literal, may be set.