From aadbb7644c0730a5ea736ce3ad74e85e3378eeb2 Mon Sep 17 00:00:00 2001 From: Tal Nordan Date: Mon, 24 Aug 2020 01:03:50 -0700 Subject: [PATCH] docs: fix header name for retries in gRPC services Risk Level: Low Testing: N/A Docs Changes: doc-only change Release Notes: N/A Signed-off-by: Tal Nordan --- docs/root/faq/load_balancing/transient_failures.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/root/faq/load_balancing/transient_failures.rst b/docs/root/faq/load_balancing/transient_failures.rst index 0be611892982f..998f9d36babc4 100644 --- a/docs/root/faq/load_balancing/transient_failures.rst +++ b/docs/root/faq/load_balancing/transient_failures.rst @@ -34,7 +34,8 @@ of requests are retried, how many times the request should be retried, timeouts Retries in gRPC services ------------------------ -For gRPC services, Envoy looks at the gRPC status in the response and attempts a retry based on the statuses configured in *x-retry-grpc-on*. +For gRPC services, Envoy looks at the gRPC status in the response and attempts a retry based on the statuses configured in +:ref:`x-envoy-retry-grpc-on `. The following application status codes in gRPC are considered safe for automatic retry.