Package io.envoyproxy.envoy.config.route.v3
package io.envoyproxy.envoy.config.route.v3
-
ClassDescriptionConfiguration for a cluster specifier plugin.Configuration for a cluster specifier plugin.Cors policy configuration.Cors policy configuration.Protobuf type
envoy.config.route.v3.Decorator
Protobuf typeenvoy.config.route.v3.Decorator
Protobuf typeenvoy.config.route.v3.DirectResponseAction
Protobuf typeenvoy.config.route.v3.DirectResponseAction
A filter-defined action type.A filter-defined action type.A simple wrapper for an HTTP filter config.A simple wrapper for an HTTP filter config.....HTTP request hedging :ref:`architecture overview <arch_overview_http_routing_hedging>`.HTTP request hedging :ref:`architecture overview <arch_overview_http_routing_hedging>`.HTTP Internal Redirect :ref:`architecture overview <arch_overview_internal_redirects>`.HTTP Internal Redirect :ref:`architecture overview <arch_overview_internal_redirects>`.[#not-implemented-hide:][#not-implemented-hide:]Query parameter matching treats the query string of a request's :path header as an ampersand-separated list of keys and/or key=value elements.Query parameter matching treats the query string of a request's :path header as an ampersand-separated list of keys and/or key=value elements.Global rate limiting :ref:`architecture overview <arch_overview_global_rate_limit>`.[#next-free-field: 12][#next-free-field: 12]The following descriptor entry is appended to the descriptor: ..The following descriptor entry is appended to the descriptor: ..The following descriptor entry is appended when the :ref:`dynamic metadata <well_known_dynamic_metadata>` contains a key value: ..The following descriptor entry is appended when the :ref:`dynamic metadata <well_known_dynamic_metadata>` contains a key value: ..The following descriptor entry is appended to the descriptor: ..The following descriptor entry is appended to the descriptor: ..The following descriptor entry is appended to the descriptor: ..The following descriptor entry is appended to the descriptor: ..The following descriptor entry is appended to the descriptor and is populated using the masked address from :ref:`x-forwarded-for <config_http_conn_man_headers_x-forwarded-for>`: ..The following descriptor entry is appended to the descriptor and is populated using the masked address from :ref:`x-forwarded-for <config_http_conn_man_headers_x-forwarded-for>`: ..The following descriptor entry is appended when the metadata contains a key value: ..The following descriptor entry is appended when the metadata contains a key value: ..Protobuf enumenvoy.config.route.v3.RateLimit.Action.MetaData.Source
The following descriptor entry is appended to the descriptor: ..The following descriptor entry is appended to the descriptor: ..The following descriptor entry is appended to the descriptor and is populated using the trusted address from :ref:`x-forwarded-for <config_http_conn_man_headers_x-forwarded-for>`: ..The following descriptor entry is appended to the descriptor and is populated using the trusted address from :ref:`x-forwarded-for <config_http_conn_man_headers_x-forwarded-for>`: ..The following descriptor entry is appended when a header contains a key that matches the ``header_name``: ..The following descriptor entry is appended when a header contains a key that matches the ``header_name``: ..The following descriptor entry is appended to the descriptor: ..The following descriptor entry is appended to the descriptor: ..Global rate limiting :ref:`architecture overview <arch_overview_global_rate_limit>`.Protobuf typeenvoy.config.route.v3.RateLimit.Override
Protobuf typeenvoy.config.route.v3.RateLimit.Override
Fetches the override from the dynamic metadata.Fetches the override from the dynamic metadata.[#next-free-field: 10][#next-free-field: 10]Protobuf enumenvoy.config.route.v3.RedirectAction.RedirectResponseCode
HTTP retry :ref:`architecture overview <arch_overview_http_routing_retry>`.HTTP retry :ref:`architecture overview <arch_overview_http_routing_retry>`.A retry back-off strategy that applies when the upstream server rate limits the request.A retry back-off strategy that applies when the upstream server rate limits the request.Protobuf typeenvoy.config.route.v3.RetryPolicy.ResetHeader
Protobuf typeenvoy.config.route.v3.RetryPolicy.ResetHeader
Protobuf enumenvoy.config.route.v3.RetryPolicy.ResetHeaderFormat
Protobuf typeenvoy.config.route.v3.RetryPolicy.RetryBackOff
Protobuf typeenvoy.config.route.v3.RetryPolicy.RetryBackOff
Protobuf typeenvoy.config.route.v3.RetryPolicy.RetryHostPredicate
Protobuf typeenvoy.config.route.v3.RetryPolicy.RetryHostPredicate
Protobuf typeenvoy.config.route.v3.RetryPolicy.RetryPriority
Protobuf typeenvoy.config.route.v3.RetryPolicy.RetryPriority
A route is both a specification of how to match a request as well as an indication of what to do next (e.g., redirect, forward, rewrite, etc.).A route is both a specification of how to match a request as well as an indication of what to do next (e.g., redirect, forward, rewrite, etc.).[#next-free-field: 42][#next-free-field: 42]Protobuf enumenvoy.config.route.v3.RouteAction.ClusterNotFoundResponseCode
Specifies the route's hashing policy if the upstream cluster uses a hashing :ref:`load balancer <arch_overview_load_balancing_types>`.Specifies the route's hashing policy if the upstream cluster uses a hashing :ref:`load balancer <arch_overview_load_balancing_types>`.Protobuf typeenvoy.config.route.v3.RouteAction.HashPolicy.ConnectionProperties
Protobuf typeenvoy.config.route.v3.RouteAction.HashPolicy.ConnectionProperties
Envoy supports two types of cookie affinity: 1.Envoy supports two types of cookie affinity: 1.CookieAttribute defines an API for adding additional attributes for a HTTP cookie.CookieAttribute defines an API for adding additional attributes for a HTTP cookie.Protobuf typeenvoy.config.route.v3.RouteAction.HashPolicy.FilterState
Protobuf typeenvoy.config.route.v3.RouteAction.HashPolicy.FilterState
Protobuf typeenvoy.config.route.v3.RouteAction.HashPolicy.Header
Protobuf typeenvoy.config.route.v3.RouteAction.HashPolicy.Header
Protobuf typeenvoy.config.route.v3.RouteAction.HashPolicy.QueryParameter
Protobuf typeenvoy.config.route.v3.RouteAction.HashPolicy.QueryParameter
Deprecated.Protobuf typeenvoy.config.route.v3.RouteAction.MaxStreamDuration
Protobuf typeenvoy.config.route.v3.RouteAction.MaxStreamDuration
The router is capable of shadowing traffic from one cluster to another.The router is capable of shadowing traffic from one cluster to another.Allows enabling and disabling upgrades on a per-route basis.Allows enabling and disabling upgrades on a per-route basis.Configuration for sending data upstream as a raw data payload.Configuration for sending data upstream as a raw data payload.[#next-free-field: 18][#next-free-field: 18]This can be used in route matcher :ref:`VirtualHost.matcher <envoy_v3_api_field_config.route.v3.VirtualHost.matcher>`.This can be used in route matcher :ref:`VirtualHost.matcher <envoy_v3_api_field_config.route.v3.VirtualHost.matcher>`.[#next-free-field: 16][#next-free-field: 16]An extensible message for matching CONNECT or CONNECT-UDP requests.An extensible message for matching CONNECT or CONNECT-UDP requests.Protobuf typeenvoy.config.route.v3.RouteMatch.GrpcRouteMatchOptions
Protobuf typeenvoy.config.route.v3.RouteMatch.GrpcRouteMatchOptions
Protobuf typeenvoy.config.route.v3.RouteMatch.TlsContextMatchOptions
Protobuf typeenvoy.config.route.v3.RouteMatch.TlsContextMatchOptions
Specifies a routing scope, which associates a :ref:`Key<envoy_v3_api_msg_config.route.v3.ScopedRouteConfiguration.Key>` to a :ref:`envoy_v3_api_msg_config.route.v3.RouteConfiguration`.Specifies a routing scope, which associates a :ref:`Key<envoy_v3_api_msg_config.route.v3.ScopedRouteConfiguration.Key>` to a :ref:`envoy_v3_api_msg_config.route.v3.RouteConfiguration`.Specifies a key which is matched against the output of the :ref:`scope_key_builder<envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.ScopedRoutes.scope_key_builder>` specified in the HttpConnectionManager.Specifies a key which is matched against the output of the :ref:`scope_key_builder<envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.ScopedRoutes.scope_key_builder>` specified in the HttpConnectionManager.Protobuf typeenvoy.config.route.v3.ScopedRouteConfiguration.Key.Fragment
Protobuf typeenvoy.config.route.v3.ScopedRouteConfiguration.Key.Fragment
Protobuf typeenvoy.config.route.v3.Tracing
Protobuf typeenvoy.config.route.v3.Tracing
Protobuf typeenvoy.config.route.v3.Vhds
Protobuf typeenvoy.config.route.v3.Vhds
A virtual cluster is a way of specifying a regex matching rule against certain important endpoints such that statistics are generated explicitly for the matched requests.A virtual cluster is a way of specifying a regex matching rule against certain important endpoints such that statistics are generated explicitly for the matched requests.The top level element in the routing configuration is a virtual host.The top level element in the routing configuration is a virtual host.Protobuf enumenvoy.config.route.v3.VirtualHost.TlsRequirementType
Compared to the :ref:`cluster <envoy_v3_api_field_config.route.v3.RouteAction.cluster>` field that specifies a single upstream cluster as the target of a request, the :ref:`weighted_clusters <envoy_v3_api_field_config.route.v3.RouteAction.weighted_clusters>` option allows for specification of multiple upstream clusters along with weights that indicate the percentage of traffic to be forwarded to each cluster.Compared to the :ref:`cluster <envoy_v3_api_field_config.route.v3.RouteAction.cluster>` field that specifies a single upstream cluster as the target of a request, the :ref:`weighted_clusters <envoy_v3_api_field_config.route.v3.RouteAction.weighted_clusters>` option allows for specification of multiple upstream clusters along with weights that indicate the percentage of traffic to be forwarded to each cluster.[#next-free-field: 13][#next-free-field: 13]