WatsonWebsocket currently relies on websocket support being present in the underlying operating system. Windows 7 does not support websockets.
SSL
SSL is supported in WatsonWebsocket. The constructors for and accept a indicating whether or not SSL should be enabled. Since websockets, and as a byproduct WatsonWebsocket, use HTTPS, they rely on certificates within the certificate store of your operating system. A test certificate is provided in both the and projects which can be used for testing purposes. These should NOT be used in production.
WatsonWsServer
WatsonWsClient
bool
TestClient
TestServer
For more information on using SSL certificates, please refer to the wiki.
New in v4.0.x
Breaking changes
Clients now identified by Guid in ClientMetadata
ListClients now returns full ClientMetadata
Send* methods now take guid as opposed to IpPort
Add targeting for .NET 7.0 and .NET Framework 4.8
Fix for Blazor WASM, thank you @ebarale99
Fix for invalid control characters, thank you @WarstekHUN
server = new WatsonWsServer("http://localhost:9000/");
server.Start();
let socket = new WebSocket("ws://localhost:9000/test/");
socket.onopen = function () { console.log("success"); };
socket.onmessage = function (msg) { console.log(msg.data); };
socket.onclose = function () { console.log("closed"); };
// wait a moment
socket.send("Hello, world!");
Accessing from Outside Localhost
When you configure WatsonWebsocket to listen on 127.0.0.1 or localhost, it will only respond to requests received from within the local machine.
To configure access from other nodes outside of localhost, use the following:
Specify the exact DNS hostname upon which WatsonWebsocket should listen in the Server constructor. The HOST header on incoming HTTP requests MUST match this value (this is an operating system limitation)
If you want to listen on more than one hostname or IP address, use * or +. You MUST:
Run WatsonWebsocket as administrator for this to work (this is an operating system limitation)
Use the server constructor that takes distinct hostname and port values (not the URI-based constructor)
If you want to use a port number less than 1024, you MUST run WatsonWebsocket as administrator (this is an operating system limitation)
If you listen on an interface IP address other than 127.0.0.1, you MAY need to run as administrator (this is operating system dependent)
Open a port on your firewall to permit traffic on the TCP port upon which WatsonWebsocket is listening
You may have to add URL ACLs, i.e. URL bindings, within the operating system using the netsh command:
Check for existing bindings using netsh http show urlacl
Add a binding using netsh http add urlacl url=http://[hostname]:[port]/ user=everyone listen=yes
Where hostname and port are the values you are using in the constructor
If you are using SSL, you will need to install the certificate in the certificate store and retrieve the thumbprint
