Currently, there is no support for the client websocket binding, it is due to missing implementation in the cpprestsdk. I have been attempting to patch the cpprestsdk to add this feature, unfortunately, when I tested the client websocket binding, it was still using the available network interface instead the one specified.
Even if that work, we have no idea how long will cpprestsdk merge the patch.
So for now, we are leaving the client websocket binding out. Users can specify the binding interface via the client_address and the server_address in the settings JSON.
where
client_address - IP address of the network interface to bind client connections for Linux (no websocket support)
server_address - IP address of the network interface to bind server connections
Currently, there is no support for the client websocket binding, it is due to missing implementation in the cpprestsdk. I have been attempting to patch the cpprestsdk to add this feature, unfortunately, when I tested the client websocket binding, it was still using the available network interface instead the one specified.
Even if that work, we have no idea how long will cpprestsdk merge the patch.
So for now, we are leaving the client websocket binding out. Users can specify the binding interface via the
client_addressand theserver_addressin the settings JSON. whereclient_address- IP address of the network interface to bind client connections for Linux (no websocket support)server_address- IP address of the network interface to bind server connections