Failed to publish bot with LUIS from behind a firewall

Describe the bug

I use the Bot Framework Composer on the Windows PC with a corporate firewall. I already set up proxy configuration as environmental variables below:

HTTPS_PROXY=http://11.22.33.44:3128
HTTP_PROXY=http://11.22.33.44:3128
NO_PROXY=localhost

So most communication has no problem, but publishing the bot with LUIS is always failed with getaddrinfo EAI_AGAIN error. The error message is below:

Sorry, something went wrong with publishing. Try again or exit out of this task. request to https://westus.api.cognitive.microsoft.com/luis/authoring/v3.0-preview/apps/import?appName=ToDoBotWithLuisSample-0(composer)-additem.en-us.lu failed, reason: getaddrinfo EAI_AGAIN westus.api.cognitive.microsoft.com

I think the cause is not to go through the proxy when communicating with the LUIS API. I think getaddrinfo should not be called on the environment behind a proxy.

Version

Bot Framework Composer

Version:  1.0.2
Electron: 8.2.4
Chrome: 80.0.3987.165
NodeJS: 12.13.0
V8: 8.0.426.27-electron.0

Browser

• Electron distribution
• Chrome
• Safari
• Firefox
• Edge

OS

• macOS
• Windows
• Ubuntu

To Reproduce

Steps to reproduce the behavior:

1. Set up proxy configuration as environmental variables on the PC with a corporate firewall
2. Run the Bot Framework Composer on the PC
3. Create bot from “Todo with LUIS” template
4. Click [Start Bot]
5. Set valid LUIS Authoring key (or any dummy string) on the [Publish LUIS models] dialog, then click [OK]
6. See error

Expected behavior

The publish will succeed. (or failed due to the dummy Authoring key)

Screenshots

Additional context

[luhan2017]

@cwhitten This is a nodejs proxy issue, I was investigating a similar proxy issue with credit-suisse recently, we sent a private electron to them to verify if the solution works, once verified, we will submit a PR in composer to support the nodejs proxy feature.

@soappp , please let me know if you want to try out our private electron, I can send you the exe and the steps to enable proxy for composer. Thanks.

[sudhanrv]

@feich-ms Let’s sync offline on this, after some investigation, we found that we’d better support the proxy settings from the bf cli side. Then composer can leverage the capability.

@luhan2017 Could you please help me as well support the proxy settings from the bf cli side. I am facing the exact same failure while publishing LUIS from composer and I am behind corporate network firewall #7543.