-
Notifications
You must be signed in to change notification settings - Fork 73
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
clickhouse-connect 0.5.2 is not considering proxy variables #114
Comments
I'm not sure what you mean by "added http_proxy, https_proxy" -- where did you add that? Also there is not a 0.1.5 release that I know of (and it would have been very old). Do you mean a different version? A different project? In any case the current version doesn't support proxies without using a custom |
Are you talking about the environment variables HTTP_PROXY and HTTPS_PROXY? |
Yeah, its an old version. I'm deploying it in kubernetes, added these variables in deployment file is what I meant. Anyways version 0.2.7 also works with these variables. |
Thanks for the details. I'm working on a new release that should restore that functionality. It came "for free" with the requests library but that was removed and I didn't realize it was automatically handling those environment variables. |
Thanks 👍🏼 |
This should work with v0.5.7. Please re-open this issue if you have any problems. I've tested with a local http and https proxy but that doesn't guarantee it will work in all situations. |
clickhouse-connect 0.5.2 is not considering proxy variables. Added http_proxy, https_proxy. When I try with 0.1.5 version its able to connect. Could someone help with this?
Thanks in advance.
The text was updated successfully, but these errors were encountered: