From 1f22d45a3b81f9524f5ce3c6350f805bd1aed6a4 Mon Sep 17 00:00:00 2001 From: Fabrice Jammes Date: Tue, 14 Jun 2022 22:56:04 +0200 Subject: [PATCH] Update content/en/docs/tasks/extend-kubernetes/socks5-proxy-access-api.md Co-authored-by: ZSC --- .../en/docs/tasks/extend-kubernetes/socks5-proxy-access-api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/extend-kubernetes/socks5-proxy-access-api.md b/content/en/docs/tasks/extend-kubernetes/socks5-proxy-access-api.md index aa7c296676..5dddd1119a 100644 --- a/content/en/docs/tasks/extend-kubernetes/socks5-proxy-access-api.md +++ b/content/en/docs/tasks/extend-kubernetes/socks5-proxy-access-api.md @@ -88,7 +88,7 @@ you configured. For this to work, the tool must support SOCKS5 proxying. {{< note >}} In the URL https://localhost:6443/api, `localhost` does not refer to your local client computer. -Instead, it refers to the endpoint on the remote server knows as `localhost`. +Instead, it refers to the endpoint on the remote server known as `localhost`. The `curl` tool sends the hostname from the HTTPS URL over SOCKS, and the remote server resolves that locally (to an address that belongs to its loopback interface). {{}}