.. _faq_why_is_envoy_404ing_connect_requests: Why is Envoy sending 404s to CONNECT requests? ============================================== Envoy's default matchers match based on host and path. Because CONNECT requests (generally) do not have a path, most matchers will fail to match CONNECT requests, and Envoy will send a 404 because the route is not found. The solution for HTTP/1.1 CONNECT requests, is to use a :ref:`connect_matcher ` as described in the CONNECT section of the :ref:`upgrade documentation`.