-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
NSIS auto-update doesn't use system HTTP proxy #959
Comments
Yes. We must not use node http API, but instead use chromium electron API. |
So I spend some time looking into this feature and assuming you haven't started any work on this, I would propose and do the following:
So then this IF will have to be used by all Providers and Publishers |
Yes. Electron Chrome Network API mimics node, so should be easy to migrate existing helpers publish/restApiRequest and util/httpRequest. |
Yes, my point was, that it should be done in a manner where it's possible to use normal HTTP, as net api requires app ready event, also when the app is building or the tests are running there is no electron app, I will create the PR either during the weekend or latest on monday |
Hi to all,
This works in the entire electron app. I can see the logs on squid. AutoUpdater should use Electron Chrome Network API but in my case this not works, the method 'checkForUpdates' of AutoUpdater bypass the proxy. Is there something that I miss ? |
I have same issue with maurovitale. |
Excuse me putting a comment on this closed issue but I found a solution to indicate a default proxy (for Electron) from program code as below.
|
The updater seems to have its own netSession, so changes on This is entirely undocumented, so the API might not be stable or internal, but for now (electron-updater@4.3.9) the following works:
If your proxy requires authentication you'll need something like this additionally:
|
The NSIS auto-updater appears not to use a system HTTP proxy if Windows is set up with one and instead tries to connect to the update URL directly. On machines where the only web access is via the proxy, this means the app will just not update (even though the embedded chromium appears to use the proxy).
The text was updated successfully, but these errors were encountered: