From ee1de179eda7ad03edc8cef4e50be6e0c6df5b52 Mon Sep 17 00:00:00 2001 From: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com> Date: Wed, 4 Aug 2021 10:44:06 -0700 Subject: [PATCH] Update website/content/docs/connect/proxies/integrate.mdx Co-authored-by: Blake Covarrubias --- website/content/docs/connect/proxies/integrate.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/connect/proxies/integrate.mdx b/website/content/docs/connect/proxies/integrate.mdx index 9951de1b28..f4d1767e70 100644 --- a/website/content/docs/connect/proxies/integrate.mdx +++ b/website/content/docs/connect/proxies/integrate.mdx @@ -55,7 +55,7 @@ transport layer. The proxy can authorize the connection by either calling the [`/v1/agent/connect/authorize`](/api/agent/connect) API endpoint or by querying the [intention match API](/api/connect/intentions#list-matching-intentions) endpoint. -The [`/v1/agent/connect/authorize`](/api/agent/connect) endpoint should be called in the connection path. +The [`/v1/agent/connect/authorize`](/api/agent/connect) endpoint should be called in the connection path for each received connection. If the local Consul agent is down or unresponsive, the success rate of new connections will be compromised. The agent uses locally-cached data to authorize the connection and typically responds in microseconds. As a result, the TLS handshake typically spans microseconds.