Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
net module #7577
Currently, Electron apps developers are expected to use the native Node.js, or other helper libraries built on top of it, to issue their HTTP(S) requests. However, it is widely known that Node.js provides a quite minimal support for web proxies.
Using Chromium network stack offers substantial advantages over the HTTP/HTTPS implementation of Node.js, specifically regarding web proxies’ support. Following is a non-exhaustive list of such features:
While it is possible to provide support for most of the previously listed features on top of Node.js, eventually using additional npm packages, the task is not trivial and requires a substantial development effort and testing. Moreover, we are not aware of any public npm package that solves the authenticating proxies’ issue.
The initial design of Node.js as server-side platform explains while it has always lacked reasonable support for web proxies as the latters are typically deployed in client environments.
Electron, being primarily targeted as a client-side framework, is expected to provide a robust networking API capable of automatically handling all issues introduced by usage of web proxies.
The present module solves all of the aforementioned problems. The API is quite simple and greatly mimics the familiar Node.j HTTP. So no substantial learning effort is required.
On the other hand, applications willing to use the new module would automatically benefit from a robust and widely used networking layer targeted for client-side environments.
Awesome. Am I correct to think this means requests using the
It may be worthwhile to explicitly document the specific API differences between