Comment 4 for bug 1439447

I talked with Eric about this and we had a couple thoughts:

1 - If the user goes through the trouble to specify an http proxy, I'm not sure it's appropriate for juju to "override" that setting, even for the bootstrap node. It should be up to the user to set up the proxy to handle private addresses. I believe this was Nate's thought on this too.

2 - If we decide that we want juju to override the proxy settings for the bootstrap node, it might be better to add it to the no_proxy list so that any future communication to the bootstrap node that happens doesn't also run into this problem.

I can start on a patch for point #2, but would like feedback on the first point as I think that's the more correct answer.