As nwjs starts it opens a tcp port on local host (for remote debugging / devtools) and listens on it.
I would prefer to be able to supply a command line switch that will tell nwjs not to open the port.
Motivation: Enterprise organizations with high security restrictions (e.g. banks) many times prevent end users from running apps that try to open and listen on ports (even on local host).
Note: At first I thought it is solely a Chromium issue (see: https://code.google.com/p/chromium/issues/detail?id=503566) however it seems that running a simple chromium installation doesn't open the mentioned port - so I guess this behavior is determined somewhere in the nwjs integration?
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
As nwjs starts it opens a tcp port on local host (for remote debugging / devtools) and listens on it.
I would prefer to be able to supply a command line switch that will tell nwjs not to open the port.
Motivation: Enterprise organizations with high security restrictions (e.g. banks) many times prevent end users from running apps that try to open and listen on ports (even on local host).
Note: At first I thought it is solely a Chromium issue (see: https://code.google.com/p/chromium/issues/detail?id=503566) however it seems that running a simple chromium installation doesn't open the mentioned port - so I guess this behavior is determined somewhere in the nwjs integration?
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.