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 authentication - understanding of workflow #216

Closed
wumpz opened this issue May 13, 2019 · 1 comment
Closed

proxy authentication - understanding of workflow #216

wumpz opened this issue May 13, 2019 · 1 comment

Comments

@wumpz
Copy link

wumpz commented May 13, 2019

We want to use the new proxy authentication possibility of getdown 1.8.3.

The problem is, that getdown does download our application artifacts from our servers using the configured proxy with its authentication. But our application itself needs this proxy authentication / configuration as well. GetDown somehow does not send proxy settings to our application. How to achieve this? GetDown starts the application within a new process.

@samskivert
Copy link
Member

As you have presumably discovered, Getdown passes the proxy info on to the app via the http.proxyHost etc. system properties. Hopefully this addresses your issue. If not, feel free to comment and reopen this issue.

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