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
Currently, the server binds to the default of all interfaces, due to having an empty host parameter in the web.TCPSite invocation. This is insecure in case of servers spanning multiple networks, as some may have external access.
Recently, the local_ip argument was added, which specifies the correct IP for the A/C to talk to the server. We can use that as well to bind to that IP specifically with a simple change like below (this also solves the issue of people being confused by the functionality of this parameter):
Currently, the server binds to the default of all interfaces, due to having an empty
host
parameter in theweb.TCPSite
invocation. This is insecure in case of servers spanning multiple networks, as some may have external access.Recently, the
local_ip
argument was added, which specifies the correct IP for the A/C to talk to the server. We can use that as well to bind to that IP specifically with a simple change like below (this also solves the issue of people being confused by the functionality of this parameter):Alternatively, a new option can be added similar to
--port
, e.g.--host
to specify that on startup.Would it be possible to add this to the codebase?
The text was updated successfully, but these errors were encountered: