I wrote my own ASP.NET ASP.NET application that will serve port 80. This is a limitation of the closed network on which it will be deployed.
The application works fine, but suddenly during testing, the service refused when the next error was triggered.
HTTP could not register URL http://+:80/ because TCP port 80 is being used by another application.
Indeed, we found that Skype was running on this test computer and was listening on port 80. Killing Skype resolved the situation. However, during deployment, we cannot guarantee that our application will have port 80 for itself.
So my question is: Is it possible to configure self-hosted WebApi to share listening on port 80?
source share