none
Getting error with WCF RRS feed

  • Question

  • I am getting the following error when I attempt to run WCF locally.  I have not tried publishing this service.  Below is the error:

    Could not find a base address that matches scheme https for the endpoint with binding MetadataExchangeHttpsBinding. Registered base address schemes are [http].

    Below is my config file:

    <system.serviceModel>
        <bindings>
          <wsHttpBinding>
            <binding name="securingWSHttpBinding"  >
              <security mode="TransportWithMessageCredential">
                <transport clientCredentialType="Windows"/>
              </security>
            </binding>
          </wsHttpBinding>
        </bindings>
        <services>
          <service behaviorConfiguration="ServiceBehavior" name="WCFBatchDataMaintenanceToolService.BDMToolService">
            <endpoint address="" binding="wsHttpBinding" contract="WCFBatchDataMaintenanceToolService.IBDMToolService"/>
            <endpoint address="mex" binding="mexHttpsBinding" contract="IMetadataExchange" />
          </service>
        </services>
        <behaviors>
          <serviceBehaviors>
            <behavior name="ServiceBehavior">
              <!-- To avoid disclosing metadata information, set the value below to false and remove the metadata endpoint above before deployment -->
              <serviceMetadata httpGetEnabled="true"/>
              <!-- To receive exception details in faults for debugging purposes, set the value below to true.  Set to false before deployment to avoid disclosing exception information -->
              <serviceDebug includeExceptionDetailInFaults="false"/>
            </behavior>
          </serviceBehaviors>
        </behaviors>
      </system.serviceModel>

    Any help would be grateful.  


    Robert Johnston

    Thursday, December 5, 2013 6:35 PM

Answers

  • Hello Robert,

    As you have httpGetEnabled on your service behaviour, I suggest removing the <endpoint address="mex" /> node altogether.  You do not have to specify both.

    This is assuming you want to browse the wsdl at http://something/myservice.svc?wsdl


    Jeff

    Thursday, December 5, 2013 9:27 PM
  • Hi,

    As @chilberto said, please try to remove your mex endpoint and just use the following:

    <serviceMetadata httpsGetEnabled="true" httpsGetUrl="https://localhost/CalcSSL/CalcSSLService.svc"/>

    Then you can just call your wcf service by using the httpsGetUrl:
    https://localhost/CalcSSL/CalcSSLService.svc.

    Best Regards,
    Amy Peng


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Friday, December 6, 2013 6:15 AM
    Moderator

All replies

  • Hello Robert,

    As you have httpGetEnabled on your service behaviour, I suggest removing the <endpoint address="mex" /> node altogether.  You do not have to specify both.

    This is assuming you want to browse the wsdl at http://something/myservice.svc?wsdl


    Jeff

    Thursday, December 5, 2013 9:27 PM
  • Hi,

    As @chilberto said, please try to remove your mex endpoint and just use the following:

    <serviceMetadata httpsGetEnabled="true" httpsGetUrl="https://localhost/CalcSSL/CalcSSLService.svc"/>

    Then you can just call your wcf service by using the httpsGetUrl:
    https://localhost/CalcSSL/CalcSSLService.svc.

    Best Regards,
    Amy Peng


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Friday, December 6, 2013 6:15 AM
    Moderator