No provision for specifying HTTP proxy for machines behind firewall

[asana]

No provision for specifying HTTP proxy for machines behind firewall

[marcogallotta]

This is a good suggestion. It might be best for our methods to take requestOptions and add them all as parameters to request. This would allow people to configure proxies, # of http agents, or anything else.

We aren't going to prioritise this right now, but would gladly accept a PR if you're interested in contributing.

[harshu108]

I would gladly do it for you, just need little context about how you want to get it done...Your design is little complicated, a little context would help.

Also need to know, how long will it take to close the pull request and incorporate the changes?

[slobak]

The design is meant to make it easy to apply options to all request by default while still preserving the flexibility and forward-compatibility to support other options, or per-request overrides.

Protocol-related things like this should follow this pattern, and thus they should be part of the configuration of the Dispatcher. If you look at the Dispatcher constructor you'll see it takes options, which it then uses in its dispatch method to configure the params passed to request. So I'd recommend adding another option to dispatcher for this, and using it in the appropriate place. Follow the model of the other options there.

Is that enough to go on?

[cw-sebastian]

Also need this feature.
Pull request is on its way :)