-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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.
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
Setting proxy parameters is not flexible enough #1446
Comments
I am developing these features and will send PR today. |
It would have made sense if there was a |
For more complex dialing protocols that don't work with our built-in proxy support, we would recommend using the WithContextDialer dial option. |
@dfawley If gRPC for Go is not going to provide any more flexible ways for doing this, could source file |
As part of the CNCF, I believe we are required to keep this license on all code contributed to the project. Note that the terms for the Apache license we use are very flexible, so if you don't want to reimplement it yourself, you can still reuse it directly as long as you follow the requirements. |
Please answer these questions before submitting your issue.
What version of gRPC are you using?
bfaf042
What version of Go are you using (
go version
)?go version go1.8.3 linux/amd64
What operating system (Linux, Windows, …) and version?
Linux
What did you do?
There are multiple grpc connections in my project at one time. One of them need proxy, another not. Proxy require credentials.
What did you see?
Currently, grpc-go takes proxy settings from ENV only once at the start of binary. In addition, it is a little bit buggy. It takes only host and ignores credentials.
What did you expect to see?
I want
The text was updated successfully, but these errors were encountered: