Envoy will attempt a retry if the gRPC status code in the response headers is “cancelled” (1)
Envoy will attempt a retry if the gRPC status code in the response headers is “deadline-exceeded” (4)
Envoy will attempt a retry if the gRPC status code in the response headers is “resource-exhausted” (8)
Generated using TypeDoc
Setting this header on egress requests will cause Envoy to attempt to retry failed requests (number of retries defaults to 1, and can be controlled by x-envoy-max-retries header or the route config retry policy). gRPC retries are currently only supported for gRPC status codes in response headers. gRPC status codes in trailers will not trigger retry logic.