joongonn/mHttp

Shutdown() doesn't free up the socket.

Opened this issue · 0 comments

In mHttp/Http/HttpBackend.cs - the Shutdown() call stops accepting new connections but doesn't close the listener outright. This causes problems if mHttp is in an application that's being run as a service as even after your service is 'stopped' any open connections won't be closed properly because the service runner is still around. It can cause the port to be permanently held open and unable to be used again until the machine is rebooted.