Problem when behind corporate proxy

[ghost]

When behind a proxy, ember try:each will not work as the HTTP request will fall in timeout.

Here is a proposition of a correction:

// index.js
'use strict';
const got = require('got');

module.exports = function(channelType, options = {}) {
  let HOST = process.env.EMBER_SOURCE_CHANNEL_URL_HOST || 'https://s3.amazonaws.com';
  let PATH = 'builds.emberjs.com';

  return got(`${HOST}/${PATH}/${channelType}.json`, Object.assign({}, { json: true }, options)).then(
    result => `${HOST}/${PATH}${result.body.assetPath}`
  );
};

Then, the user is responsible to update its own ember-try.js configuration

// config/ember-try.js
const getChannelURL = require('ember-source-channel-url');
const tunnel = require('tunnel-agent');

const options = {
  agent: tunnel.httpOverHttp({
    proxy: {
      host: 'myproxy.mycompany.com',
      port: 8080
    }
  })
};

module.exports = function() {
  return Promise.all([
    getChannelURL('release', options),
    getChannelURL('beta', options),
    getChannelURL('canary', options)
  ]).then((urls) => {
  ...

What do you think of this ?

[jelhan]

We are also running into this issue. Another option would be supporting HTTP_PROXY, HTTPS_PROXY and NO_PROXY environment variables. Most tools respect these environment variables. So it would make usage much easier, if ember-source-channel-url (and indirectly ember-try) would respect it as well.

We are having a hard-time providing a work-around because one tool used by ember-try respects the environment variables (yarn) but another one does not (ember-source-channel-url). This makes it even more difficult to use proxychains as a work-around. Because it tries route a network request through a proxy twice if the program supports proxy through the environment variables as well.