Binding to port 80 or 443 about fleck HOT 9 CLOSED

Fleck could bind to those ports. The issue is sharing them with a webserver.

As for sharing them easily, that would require some large changes. Specifically, to share port 80 or 443 on windows would require interfacing with http.sys. That's exposed through HttpListener. Switching from Sockets to HttpListener would take a bit of effort. Also, I'm uncertain how the http.sys stack would handle a websocket connection.

One possible option, if you're using something like nginx, you could reverse proxy from 80 to whatever port the websocket server is running on. There is an example blog post here.

from fleck.

Thanks for the quick and elaborate answer. using a reverse proxy is not an option (in this case).
Hm...

from fleck.

What is your scenario? I might be able to help.

from fleck.

Running Web Sockets (server) in .NET code on 80 and 443 without a reverse proxy - simple as that :)
.NET 4.5 will bring support - but only for Windows 8...

from fleck.

Hm, seems not to be too easy...

from fleck.

Just setting the port to 80 or 443 works fine if no other processes are using the port.

from fleck.

Nope - then I get this (for port 80 - IIS is stopped):

System.Net.Sockets.SocketException (0x80004005): An attempt was made to access a socket in a way forbidden by its access permissions

from fleck.

Sorry, it works. SQL Server Reporting Services was blocking it :(

from fleck.

Yeah, it's a rather strange exception message that is given when port 80 is taken. Glad you figured it out.

from fleck.