You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by psiservices-ccounterman March 1, 2023
I'm having problems with people running my electron app behind a proxy. I've fixed some issues by using https://www.electronjs.org/docs/latest/api/net which "is similar to the HTTP and HTTPS modules of Node.js but uses Chromium's native networking library instead of the Node.js implementation, offering better support for web proxies."
I'm fixing more, but realized that it is affecting the logging as well.
src/transports/remote.js uses http and https.
Before I do anything difficult, is there a currently-supported way to swap in the electron net API or substitute a different remote transport?
Is there a reason electron-log shouldn't use electron.net as the norm?
The text was updated successfully, but these errors were encountered:
Discussed in #351
Originally posted by psiservices-ccounterman March 1, 2023
I'm having problems with people running my electron app behind a proxy. I've fixed some issues by using
https://www.electronjs.org/docs/latest/api/net which "is similar to the HTTP and HTTPS modules of Node.js but uses Chromium's native networking library instead of the Node.js implementation, offering better support for web proxies."
I'm fixing more, but realized that it is affecting the logging as well.
src/transports/remote.js uses http and https.
Before I do anything difficult, is there a currently-supported way to swap in the electron net API or substitute a different remote transport?
Is there a reason electron-log shouldn't use electron.net as the norm?
The text was updated successfully, but these errors were encountered: