katokay

We have recently been trying to move an existing service to use Transport security with Basic authentication. There is a deployed service http://dev.services.companyname.com/ServiceName.svc for which I can view in IE7 both at http and https urls. However, when the proxy is generated from the secure address, and when the wsdl is viewed from the secure address some of urls change to https://computername.domainname/ServiceName.svc, so when a request is made for an endpoint it cannot find the endpoint and gets a 404 on the soap action because the certificate does not validate against the latter url. Am I missing a setting somewhere I'm confused where it picks up the computer name for the URL because nowhere do I reference that computername.



Re: Windows Communication Foundation (Indigo) WsHttpBinding Transport security wsdl Address location

David Kreutz - MSFT

Can you share your wsdl






Re: Windows Communication Foundation (Indigo) WsHttpBinding Transport security wsdl Address location

Scott Seely

Whenever I run into something like this, I like to temporarily expose a ServiceMetadataBehavior attribute that allows for HttpGet. If I can see the help page and WSDL link in the browser, I know that the service is up and visible at the chosen URL. If I can't I know I have other issues.

If this does work, the next step is to turn on verbose tracing for the endpoint and hit the service with your client. The server side traces should tell you why the connection is being refused and should point you to what you need to do in order to solve the problem. I recommend using SvcConfigEditor to make the changes to get traces and then use SvcTraceViewer.exe to view the traces.