I was going through the same pain as this guy. In my case, I was trying to create a simple webapp on port 8080. But try as I may, I couldn't get around the 503 Service Unavailable response.
Luckily, the same guy also posted a response to his original blog entry.
Turns out the command netsh http show urlacl saves the day. In my case, another user on the same server had just happened to reserve port 8080 while doing some other work.
All's well...
Monday, July 12, 2010
Subscribe to:
Posts (Atom)
Posts
