Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2349
Personally, I hope we have a proxy option instead of configurations for
those URLs.
That's because, it's hard to configure every URLs for users. (not scalable
solution) There might be more URLs except for helium related thins. (e.g maven
dep loader, `%spark.dep`, ...)
If we have proxy support in Zeppelin, we just need to set that
configuration only.
> Does it make sense to use the well known environment variables http_proxy
and no_proxy? They are usually configured correctly already on all the machines
that require proxy settings. If there is a use case to have different proxy
settings for the node installer and the npm installer (although I don't have
one personally right now), we can still provide separate configuration
properties. But it would certainly come in handy to use http_proxy for all of
them if it is set and not overwritten.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
