Webservice through SSL endpoint not found with 404

I have a web service and it works, and through the browser I can contact it and see it and run it. Also without https, I can make calls to webservice.

To make calls, I am currently using a small console application to test and view the results.

On the server side, my web.config looks like this:

Service Section

<services> <service name="Website.mynamespace.Service1"> <endpoint address="/service.svc" behaviorConfiguration="" binding="wsHttpBinding" contract="SomeDLLFile.Anothernamespace.Services.Proxy.Interface1" ></endpoint> <endpoint address="/service.svc" behaviorConfiguration="" binding="wsHttpBinding" contract="SomeDLLFile.Anothernamespace.Services.Proxy.Interface1" bindingConfiguration="myBinding" /> <endpoint address="mex" binding="wsHttpBinding" contract="IMetadataExchange"/> </service> <service name="Website.mynamespace.Service2"> <endpoint address="/service.svc" behaviorConfiguration="" binding="wsHttpBinding" contract="SomeDLLFile.Anothernamespace.Services.Proxy.Interface2" ></endpoint> <endpoint address="/service.svc" behaviorConfiguration="" binding="wsHttpBinding" contract="SomeDLLFile.Anothernamespace.Services.Proxy.Interface2" bindingConfiguration="myBinding" /> <endpoint address="mex" binding="wsHttpBinding" contract="IMetadataExchange"/> </service> </services> 

Used binding

  <wsHttpBinding> <binding name="myBinding"> <security mode="Transport"> <transport clientCredentialType="None"/> </security> </binding> </wsHttpBinding> 

On the client side (my console application), I added a service link to my web service. That way I can make calls through HTTP. However, when using HTTPS, I get an error

"There was no endpoint listening at https://test.mywebsite.nl/service.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details."

app.config from my console application is as follows:

 <client> <endpoint address="https://test.mywebsite.nl/service.svc" binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_IProxyInterface1" contract="Service.IProxyInterface1" name="BasicHttpBinding_IProxyClientInterface" /> <endpoint address="https://test.mywebsite.nl/service.svc" binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_IProxyInterface2" contract="Service.IProxyInterface2" name="BasicHttpBinding_IProxyInterface2" /> </client> <behaviors> <serviceBehaviors> <!-- Step 2. Inside a <serviceBehaviors> section, add a name attribute in the <behaviors> element that matches the behaviorConfiguration attribute in the <service> element above. --> <behavior name=""> <serviceMetadata httpGetEnabled="true" httpGetUrl=""/> <serviceDebug httpHelpPageEnabled="true" includeExceptionDetailInFaults="true" /> </behavior> </serviceBehaviors> </behaviors> 

When I look at the internal exception, I look at error 404. I tried various sentences from other topics on SO, as well as articles in MS, but I must be missing something, since I'm still presented with the same error . Does anyone know what I'm doing wrong here?

0
security web-services
source share
2 answers

The problem caused by this> topic here on SO has been resolved.

The problem was the name of the service, so I combined the endpoints for both contracts in one service definition. I also changed wsHttpBinding to basicHttpBinding.

+1
source share

I had something similar, and I installed a certified SSL certificate certificate in IIS. Try:

http://weblogs.asp.net/scottgu/archive/2007/04/06/tip-trick-enabling-ssl-on-iis7-using-self-signed-certificates.aspx

Obviously, you will need to buy the appropriate certificate when you begin deployment in your production environment.

0
source share

All Articles