Skip to content

documentation: improve proxy documentation #8840

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
eshitachandwani merged 4 commits into from
Jan 29, 2026
Merged

documentation: improve proxy documentation #8840

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
9f3f3fa
improve doc
eshitachandwani Jan 16, 2026
529079a
improve sentence
eshitachandwani Jan 20, 2026
f8c1f11
improve sentence
eshitachandwani Jan 20, 2026
9bf2de5
improve docs
eshitachandwani Jan 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions Documentation/proxy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,16 @@ HTTP CONNECT proxies are supported by default in gRPC. The proxy address can be
specified by the environment variables `HTTPS_PROXY` and `NO_PROXY`. (Note that
these environment variables are case insensitive.)

**NOTE**: Using CONNECT proxies via https is not supported. gRPC performs a
plaintext CONNECT handshake to establish a tunnel and does not support the
additional encryption required to secure the initial connection to the proxy
itself.

When using TLS, the gRPC traffic is encrypted end-to-end between the client and
the destination server. Even when using a CONNECT proxy without https, the
security is not compromised, as the proxy only sees the destination address and
cannot intercept the encrypted gRPC data.

## Custom proxy

Currently, proxy support is implemented in the default dialer. It does one more
Expand Down