通过传输安全性使用Https basicHttpBinding获取404无端点侦听错误WCF 4.0

Question

I am trying to get https security working for my wcf web service hosted in IIS 7.5. I have looked through every article I can find online regarding this and tried just about every configuration or IIS trick I could find or variation. I think this might be a IIS, windows level configuration issue. We are using a wild card SSL cert like *.mycompany.com. This cert is being used on 3 other sites already in same IIS if that has any bearing. Does anyone have any idea what I am running into here??? This is a public server, non TEST and http binding works fine. I am having this same https issue on my dev and production servers. We have another https website on this production box and it sends and receives data just fine. I am getting Exception :

There was no endpoint listening at https://subdomain.mydomain.com/MyService.svc that could accept the message. This is often caused by an incorrect address or SOAP action.

Inner Exception :

The remote server returned an error: (404) Not Found.

Here is my web.config :

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
   <appSettings file="LocalAppSettings.config">
      <!--<add key="CustomIISServiceHostEndPoint" value="https://subdomain.mydomain.com/MyService.svc" />-->
   </appSettings>
   <system.web>
      <compilation debug="true" targetFramework="4.0" />
      <customErrors mode="Off" />
  </system.web>
  <system.serviceModel>
      <bindings>
  <basicHttpBinding>
    <binding name="COLWebServiceBinding" maxReceivedMessageSize="134217727" sendTimeout="00:03:00" receiveTimeout="00:03:00">
        <security mode="Transport">
           <transport clientCredentialType="None" />
        </security>
        <readerQuotas maxArrayLength="65536" maxBytesPerRead="65536" maxStringContentLength="134217727" />
     </binding>
  </basicHttpBinding>
</bindings>
<services>
  <service behaviorConfiguration="COLWebService.ServiceBehavior" name="COLWebService">
    <endpoint address="https://subdomain.mydomain.com/MyService.svc"
              binding="basicHttpBinding"
              contract="MyCompany.COLWebService.ICOLWebService"
              bindingConfiguration="COLWebServiceBinding" />
    <endpoint address="mex" binding="mexHttpsBinding" contract="IMetadataExchange" />
  </service>
</services>
<extensions>
  <behaviorExtensions>
    <add name="errorHandler" type="MyCompany.COLWebService.ErrorHandlerBehaviorExtensionElement, MyCompany.COLWebService" />
  </behaviorExtensions>
</extensions>
<behaviors>
  <serviceBehaviors>
    <behavior name="COLWebService.ServiceBehavior">
      <serviceMetadata httpsGetEnabled="true" />
      <serviceDebug includeExceptionDetailInFaults="true" />
    </behavior>
    <!--<behavior name="">
      <serviceMetadata httpGetEnabled="true" />
      <serviceDebug includeExceptionDetailInFaults="true" />
    </behavior>-->
  </serviceBehaviors>
</behaviors>
<serviceHostingEnvironment multipleSiteBindingsEnabled="false">
</serviceHostingEnvironment>
 </system.serviceModel>
 <system.webServer>
    <modules runAllManagedModulesForAllRequests="true" />
  </system.webServer> 
 </configuration>

And here is my client's app.config :

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
    <system.serviceModel>
        <bindings>
            <basicHttpBinding>
                 <binding name="wsHttpBinding_ICOLWebService" closeTimeout="00:01:00"
                openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:03:00"
                allowCookies="false" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard"
                maxBufferPoolSize="524288" maxReceivedMessageSize="134217727"
                messageEncoding="Text" textEncoding="utf-8" useDefaultWebProxy="true">
                      <readerQuotas maxStringContentLength="134217727" maxArrayLength="65536"
                    maxBytesPerRead="65536" />
                      <security mode="Transport">
                          <transport clientCredentialType="None" proxyCredentialType="None" />
                     </security>
                 </binding>
            </basicHttpBinding>
         </bindings>
        <client>
             <endpoint address="https://subdomain.mydomain.com/MyService.svc"
            binding="basicHttpBinding" bindingConfiguration="wsHttpBinding_ICOLWebService"
            contract="COLWebService.ICOLWebService" name="wsHttpBinding_ICOLWebServiceEP" />
          </client>
    </system.serviceModel>
  </configuration>

Answer 1

You can manually add host header values to SSL certificates by modifying the applicationhost.config file in system32\\inetsrv. Look for the section for your IIS instance.

Answer 2

It could be that the https binding has not been configured for the new site.

In IIS, select the site, then click on advanced settings and check the contents of Bindings. Make sure that https is in the list.

Edit

The other thing that it could be is that the svc handler is not activated. Is ASP.Net turned on for the site?

You should test it without the https first, to make sure that the problem is related to https.

Edit 2

Make sure that the site is started. Have you checked that you can access the svc via a browser.

You have several sites on the machine, all use https. Have you configured host headers to allow all sites to use https? Is https on this site on a different port?

Answer 3

Open the .svc file - I would guess its not referencing COLWebService as the service.

Your config file has:

name="COLWebService"

in the service declaration. This needs to match .SVC's named service, which looking at the url you've given, I think will be 'MyService'.

Answer 4

Your service model section should be like this

<system.serviceModel>
    <behaviors>
      <serviceBehaviors>
        <behavior name="">
          <serviceMetadata httpGetEnabled="true" httpsGetEnabled="true" httpsGetUrl="/ssl"/>
          <serviceDebug includeExceptionDetailInFaults="false"/>
          <dataContractSerializer maxItemsInObjectGraph="6553600" />
        </behavior>
      </serviceBehaviors>
    </behaviors>
    <bindings>
      <basicHttpBinding>
        <binding name="TransportSecurity" maxReceivedMessageSize="2147483647">
          <security mode="Transport">
            <transport clientCredentialType="None"/>
          </security>
        </binding>
      </basicHttpBinding>
    </bindings>
    <services>
      <service name="COLWebService.Service" behaviorConfiguration="">
        <endpoint address="/ssl" binding="basicHttpBinding" bindingConfiguration="TransportSecurity" contract="MyCompany.COLWebService.ICOLWebService"/>
        <endpoint address="mex" binding="mexHttpsBinding" contract="IMetadataExchange"/>
      </service>
    </services>
    <serviceHostingEnvironment multipleSiteBindingsEnabled="true" />
  </system.serviceModel>

And your clients will access servis over https https://subdomain.mydomain.com/MyService.svc/ssl , over http same as old https://subdomain.mydomain.com/MyService.svc