Skip to content
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

proxy configuration #420

Open
yannski opened this issue Jun 7, 2019 · 4 comments
Open

proxy configuration #420

yannski opened this issue Jun 7, 2019 · 4 comments

Comments

@yannski
Copy link
Member

yannski commented Jun 7, 2019

  1. If a proxy configuration exists on the system, it should be used
  2. Even if it exists, it should be possible to bypass it
  3. If a proxy configuration does NOT exist on the system, it should be possible to define one

Not sure about 3

@EtienneM
Copy link
Member

EtienneM commented Aug 29, 2019

Using a HTTP proxy is already possible with the three following env variable: HTTP_PROXY, HTTPS_PROXY, NO_PROXY. Did you think about something else than that?

@yannski
Copy link
Member Author

yannski commented Aug 29, 2019

will it work with HTTP_PORT and a socks URI? At least those variable should be mentionned in the doc.

@yannski
Copy link
Member Author

yannski commented Aug 29, 2019

BTW, aren't the variables named HTTP_PROXY and HTTPS_PROXY?

@EtienneM
Copy link
Member

Sorry it was a typo in my message... Variables are HTTP_PROXY and HTTPS_PROXY.

Usage of these variables is in the doc https://doc.scalingo.com/platform/cli/features

Related documentation issue: Scalingo/documentation#656

Regarding SOCKS5, I just successfully used the HTTP_PROXY variable with a local SOCKS5 proxy. I asked our customer to also test this in order to confirm it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants