Closed nicolasr75 closed 6 years ago
It was just that the IIS under which I installed had the web socket protocol deactivated! I was irritated that it still got that far. Without web socket protocol activated I would have expected it to fail much earlier. But probably that's because web sockets sit on top of http. Closing...
I have an ASP.NET Core 2.0 web app that implements a web sockets server. Then I have a .NET Core 2.0 console app that uses WebSocket4Net to connect to the web app. This worked well while I was running the web app in Visual Studio self-hosted. Now I have installed the web app in IIS (not root but a sub directory, if of any importance) and can't connect to the web sockets server anymore. The web sockets server logs the connection attempt but the client then tells me:
accept key doesn't match
Do you have any idea what the problem could be or how I could find out more about it? At this moment I have no idea how to get more diagnostic information for this :-(
Btw, thanks for this great component! Nicolas