.. _config_http_conn_man_route_table_route_matching: Route matching ============== .. attention:: This section is written for the v1 API but the concepts also apply to the v2 API. It will be rewritten to target the v2 API in a future release. When Envoy matches a route, it uses the following procedure: #. The HTTP request's *host* or *:authority* header is matched to a :ref:`virtual host `. #. Each :ref:`route entry ` in the virtual host is checked, *in order*. If there is a match, the route is used and no further route checks are made. #. Independently, each :ref:`virtual cluster ` in the virtual host is checked, *in order*. If there is a match, the virtual cluster is used and no further virtual cluster checks are made.