[Bug] Grist-core and Grist-electron behind a proxy fail some requests to remote

[emanuelegissi]

I am using Grist-core and Grist-electron behind a proxy. The http_proxy https_proxy and no_proxy environment variables are correctly set:

http_proxy=http://username:password@proxy_server_address:port
...

Telemetry request fails

I set up the telemetry in Grist-core, because I think you deserve to know who uses your wonderful tool. But telemetry requests do not consider the http_proxy, https_proxy, and no_proxy environment variables and fail.

Manifest request fails

Even if my proxy allows it, the request from both Grist-core and Grist-electron to the grist-widget repository fails:

S3 connection fails

Even if I am able to connect to the remote S3 bucket from the console with s3cmd (http://s3tools.org), Grist-core fails to connect to it due to a timeout. As a double check, I set up a local S3 bucket with Minio, and it works.

Of course, I tried the same operations without a proxy and all is ok.

IMHO, in these cases, Grist requests do not consider the http_proxy, https_proxy, and no_proxy environment variables. Unfortunately, it seems that the Node.js runtime does not support configuring HTTP proxying using environment variables out of the box. Request library support is mixed.

See stackoverflow, where the Node.js issue is described and solutions are proposed.

Thank you