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
I think you have a great project here, thanks for sharing. However, one of the key aspects of WebSockets is that they are "firewall friendly" because they use port 80 and 443. Correct me if I'm wrong, but with your class using a TcpListener at the lowest level, you won't be able to run this on port 80 if a web server is also already running on the same machine? Do you know of any workarounds for that?
The text was updated successfully, but these errors were encountered:
Thanks! Yes this is a though limitation. I do not know a way to hook into the same port that for example IIS uses.
HTTP.sys (IIS) since version 8 has this capability of switching between regular HTTP and WebSockets, but as far as I know ,there is no way to hook there. In .NET Core there may be a way, but probably using the buit-it websocket support is better idea.
I think you have a great project here, thanks for sharing. However, one of the key aspects of WebSockets is that they are "firewall friendly" because they use port 80 and 443. Correct me if I'm wrong, but with your class using a
TcpListener
at the lowest level, you won't be able to run this on port 80 if a web server is also already running on the same machine? Do you know of any workarounds for that?The text was updated successfully, but these errors were encountered: