-
Notifications
You must be signed in to change notification settings - Fork 44
Add support for proxies #80
base: master
Are you sure you want to change the base?
Conversation
|
Would love to see this fix get merged soon, as the Gitter desktop client currently doesn't work for anyone that is behind a corporate proxy. |
|
@nhu how can we test it? where does one add the proxy? |
|
@mydigitalself you can just add a proxy to your system. The old version keeps beeing white on startup because the proxy cannot resolve "app://" requests. So with the fix you bypass the system proxy for "app://" requests and you should see the login page of Gitter. For testing it on my machine i have picked a random proxy from http://proxylist.hidemyass.com/ |
|
Ah ok, cool, thanks. I'm on a loaner Macbook at the moment and don't have my full environment setup. Hopefully I'll get my machine back soon and I'll test this out for you. |
|
I'm using OS X El Capitan and after setting up the dev environment locally I ran a quick test. I ran I then fetched this PR to a branch I called After pulling down this patch, I ran I went back to the master branch and ran I also tried unloading this file with: and then ran |
|
My guess is that is the culprit. Is that something I need to adjust on my end? |
|
@nhu Does this fix still work on |
|
@MadLittleMods hi no this fix does not work because once you passed the trouble with the app framework you will stuck at the oauth2 library which doesnt support proxies. They have also pull requests pending. Here my gitter client written in es6 and hosted in electron: https://github.com/nhu/gitter2 My own oauth lib written for the client relies on request which supports proxies: https://github.com/nhu/oauthjs |
|
Any updates on this? Thanks. |
Added the app protocol which is used inside the nw.js container to the proxy whitelist.
Now proxies should work.
Fixes #49