Skip to content

Download fails in conjunction with corporate proxy #26

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

Closed
Flowkap opened this issue May 22, 2014 · 5 comments
Closed

Download fails in conjunction with corporate proxy #26

Flowkap opened this issue May 22, 2014 · 5 comments

Comments

@Flowkap
Copy link

Flowkap commented May 22, 2014

Please add proxy support.

I think itll be usefull to use npms proxy setting as it should be set as default.

@aearly
Copy link
Collaborator

aearly commented May 24, 2014

Pull requests are accepted. :)

As a workaround, you could manually download Sauce Connect for your platform and unzip it into node_modules/sauce-connect-launcher/sc/.

@Flowkap
Copy link
Author

Flowkap commented May 27, 2014

I added quick and dirty proxy support but fail to execute it on my linux -.- Seems as if sc for linux is 64 Bit?

Additionally it works perfectly for an http.request, but i get issues cocerning the https.request used in sauce-connect-launcher.js

Is there a specific reason for the https request?

PS: as its working and ok for me I make a pull request of course ;)

@aearly
Copy link
Collaborator

aearly commented May 27, 2014

It's probable that it's 64-bit. I haven't used 32-bit linux since 2005....

We use https because you'd want that when downloading executable programs -- it prevents man-in-the-middle attacks. It's a security hole otherwise. Does your proxy not transparently pass-through SSL connections?

@Flowkap
Copy link
Author

Flowkap commented Jun 10, 2014

Sorry but fixing one thing opens 3 others. Running sauceConnect on one of our servers instead of using sauce-connect-launcher.

@aearly
Copy link
Collaborator

aearly commented Jun 10, 2014

That's probably a better use-case behind a restrictive corporate proxy. Sorry we couldn't be of more use. 😞

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