From 54ded7cc4a724622fdf13cee9f4a99f176c66377 Mon Sep 17 00:00:00 2001 From: kerrick-lyft Date: Tue, 27 Sep 2016 14:29:39 -0700 Subject: [PATCH] x-envoy-upstream-rq-per-try-timeout-ms timeouts *are* retried --- docs/configuration/http_filters/router_filter.rst | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/configuration/http_filters/router_filter.rst b/docs/configuration/http_filters/router_filter.rst index b23f0d616d1c6..b56065203d00c 100644 --- a/docs/configuration/http_filters/router_filter.rst +++ b/docs/configuration/http_filters/router_filter.rst @@ -70,9 +70,7 @@ using a ',' delimited list. The supported policies are: Envoy will attempt a retry if the upstream server responds with any 5xx response code, or does not respond at all (disconnect/reset/etc.). (Includes *connect-failure* and *refused-stream*) - * **NOTE:** Envoy will not retry when a request times out (resulting in a 504 error code). This is - by design. The request timeout is an outer time limit for a request, including any retries that - take place. + * **NOTE:** Envoy will not retry when a request exceeds :ref:`x-envoy-upstream-rq-timeout-ms` (resulting in a 504 error code). Use :ref:`x-envoy-upstream-rq-per-try-timeout-ms` if you want to retry when individual attempts take too long. :ref:`x-envoy-upstream-rq-timeout-ms` is an outer time limit for a request, including any retries that take place. connect-failure Envoy will attempt a retry if a request is failed because of a connection failure to the upstream