Add gRFC for HTTPS proxy support. #530
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Member
|
We can't look at this until you sign the CLA. |
atollena
reviewed
Jan 14, 2026
Contributor
atollena
left a comment
atollena
left a comment
There was a problem hiding this comment.
This is something that datadog would benefit from for some internal use cases that currently use double proxying with a sidecar, so I'm supportive of it. Happy to help with the Go API, although you can probably focus on a single language (c-core).
| Many proxy deployments support HTTPS connections, where the client establishes a TLS connection to the proxy before sending the HTTP CONNECT request. This ensures that: | ||
| 1. Proxy authentication credentials are encrypted | ||
| 2. The target hostname in the CONNECT request is not visible to network observers | ||
| 3. The proxy can be authenticated via its TLS certificate |
Contributor
There was a problem hiding this comment.
The proxy can also identify the client from its client TLS certificate, if provided. The identity can then be used the same way as basic proxy auth, and replace it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a gRFC for HTTPS proxy support where the connection to the proxy itself is TLS-encrypted. This ensures that proxy authentication credentials (such as BasicAuth username and password) are transmitted securely rather than in plaintext.
The C implementation is provided in this PR: grpc/grpc#41377
This adresses issue grpc/grpc#30347