-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
proxy configuration #32
Comments
since we use request, it should be a simple fix: |
thanks for getting back so quickly, I will try it out! |
this may be on our side @deq9z :) not sure you can solve it yourself through the UI. i was commenting that for the developers of rest-client ;) |
yeah, I was looking in the UI code, then in the atom/package/rest-client/node_modules/request/index.js code to see if I could inject it there locally for getting myself up & running. |
This would be nice for starting the Advanced options partial view. :-) |
Running into the same issue. Any news on this? |
Hi! I'll take a look. |
GET http://www.google.ca
result pane: Error: connect ETIMEDOUT XXX.XXX.XXX.XXX:80
I have configured atom.io to leverage the corporate proxy, have no problems connecting outbound to install packages, however; running into a timeout using rest-client package. I am speculating that it is due to no proxy configuration in the code.
The text was updated successfully, but these errors were encountered: