Reputation: 31
I need a suggestion regarding the hosting wcf rest service on port 80. I devloped a service and I am hosting this service as windows service on port 80 and this service wouldn't talk to the outside world. The communication is between local browser and service. In windows 7 and later versions I am using netsh
and in XP I am using httpcfg
to reserve namepsace on port 80.
If I distribute this to every one would it work on every machine. Is it the correct approch? What are the pros and cons in this approach?
I am suposed to use port 80 only.
Upvotes: 0
Views: 1409
Reputation: 6552
I wouldn't host anything on a commonly know ports this is a bad idea. Since the service isn't talking to the outside world you can choose a port that isn't in use by another service.
Upvotes: 0
Reputation:
Port 80 is used by default to serve HTTP requests, its not part of the Hypertext Transfer Protocol but still... its widely use for that purpose. I would not recommend you to continue with your current aproach since you want to distribute this piece of software, the end-user is likely to find a lot of problems, any software/service running on the machine binded to port 80 would not allow yours to attach.
I would investigate which port its more likely NOT used by any other protocol or if the requirement allows it, make a local scan for any free port and use that.
Upvotes: 1