Found HTTP Status Code - 302.

Moved Permanently HTTP Status Code - 301.

Permanent Redirect HTTP Status Code - 308.

See Other HTTP Status Code - 303.

Temporary Redirect HTTP Status Code - 307.

HTTP status code - 404 Not Found.

HTTP status code - 503 Service Unavailable.

All requests must use TLS.

External requests must use TLS.

No TLS requirement for the virtual host.

.

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_rate_limit>`.

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 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 to the descriptor: .

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

Specifies the route's hashing policy if the upstream cluster uses a hashing :ref:`load balancer <arch_overview_load_balancing_types>`.

Envoy supports two types of cookie affinity: 1.

The router is capable of shadowing traffic from one cluster to another.

HTTP retry :ref:`architecture overview <arch_overview_http_routing_retry>`.

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.

Compared to the :ref:`cluster <envoy_api_field_route.RouteAction.cluster>` field that specifies a single upstream cluster as the target of a request, the :ref:`weighted_clusters <envoy_api_field_route.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.