title: WCF WSDL location address with HTTPS
body: <p>A common issue for WCF appears to be how the hostname is resolved within the wsdl for the links to other files. The issue is that the machine name of the computer is placed into the wsdl to link the other wsdl files, so if you visit <strong><a href="http://myhost/service.svc" rel="noreferrer">http://myhost/service.svc</a></strong> it may point to the rest of the wsdl on another location, <strong>ie <a href="http://mypc/service.svc?wsdl" rel="noreferrer">http://mypc/service.svc?wsdl</a></strong> which obviously is something you cannot see externally.</p>
  
  <p>There are a few solutions out there for this already, this being the common one. Where you can setup the host header.</p>
  
  <ul>
  <li><a href="http://jberke.blogspot.com/2008/06/wsdl-for-wcf-aspnet-service-uses-local.html" rel="noreferrer">http://jberke.blogspot.com/2008/06/wsdl-for-wcf-aspnet-service-uses-local.html</a></li>
  </ul>
  
  <p>My question is, how can i work around this when using an external IP. I'm connecting to a clients head-office from their website to retrieve data, its not setup with a dns etc and the ip re-routes to a machine internally. Is there any way to force the machine hosting the WCF to present the external address in the wsdl files rather than the machine name?</p>
  
  <p>I'm using SSL for the connection, which may make a difference (as with the host headers).</p>