Wcf – WSDL from WCF Issue

Well, I still can't get it to work on the Vista servers - it's still giving 503 errors, but I ended up getting it setup on a Windows 2003 server, and it seems to be working now.

One thing I did learn in this process was the use of HttpCfg.exe to allow a user to open a non-standard HTTP port.

Basically I had to run something like the following command:

httpcfg.exe set urlacl /u http://+:5555/ /a "O:AOG:DAD:(A;;RPWPCCDCLCSWRCWDWOGA;;;S-1-0-0)"

You can then view the URL ACL settings with this command:

httpcfg.exe query urlacl

On Vista, you can run the same types of commands using netsh (see link below).

Sadly, this took awhile to figure out, but it was a good learning experience.

Here are some links that I thought were useful in figuring this out:

• http://www.leastprivilege.com/HttpCfgACLHelper.aspx
  • This explians how to get the SID for your user account (for the /a part of the command. Coincidentally, this is easier on Vista - you can just specify the domain\user in the netsh http set urlacl command
• http://technet.microsoft.com/en-us/library/cc781601.aspx
  • This explains the syntax/options of the HttpCfg.exe command
• http://msdn.microsoft.com/en-us/library/ms733768.aspx
  • This really explains everything you need to know for HttpCfg/netsh http
• http://blogs.msdn.com/drnick/archive/2006/04/14/configuring-http.aspx
  • Similar info to the msdn link above, but provides more explanation, and more relation to WCF
• http://dotnet.dzone.com/news/msmq-wcf-and-iis-getting-them-
  • Another description of WCF and HTTP (and MSMQ), with a focus on IIS

When you say "added a WebHttpBinding class", it sounds like you are doing a lot of the configuration in code as opposed to in configuration files.

If this is the case, you could try moving the configuration to the configuration file. Then create 2 endpoints for the contract one REST and one SOAP, with 2 different addresses and bindings.