Closed deizel closed 11 years ago
I'm not too knowlegeable on how proxies work, but Tern is trying to connect to localhost
here, I don't think the proxy kicking in for local connections is a very sane thing. It definitely won't work, even with proper proxy settings (the proxy server won't know what localhost is).
Ah, that makes sense - I see now where it tries to connect to localhost
.
According to the Python documentation (v2/v3)
proxies=None
defaults to the environmental proxy settingsproxies={}
(passing an empty dictionary) disables proxy autodetectionI'm not at my work machine to try it right now, but it would seem the latter is the way to go here.
Indeed (though I'm still amazed that it would look at proxy settings at all when connecting to localhost). Can you report on whether adding that argument helps? If so, I'll add it to the code (both here and in the vim plugin).
So, the suggested changes did the trick here for me - see pull request.
I did find afterwards that setting the Unix-like NO_PROXY
environment variable was another solution:
However, there may be other corporate users like me that don't have control over their proxy settings (inetcpl.cpl
and regedit.exe
are locked down).
Just a heads up...
When I make a new *.js file and press 'a', I get this error message from what looks like my corporate proxy server:
IIRC, Package Control seems to use the system proxy settings correctly out of the box.
I'm not really sure what is going on here as I can't see the
<body>
of the error message.