Click here to Skip to main content
15,887,485 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
I made a web service that seemed to be working fine until i decided to use wsHttpBinding so that i could have the extra security. After changing the binding to wsHttpBinding everything continued to work on Win 7 clients but the Win XP clients are not working. Below is my web.config.

<pre lang="xml">
<?xml version="1.0"?>
<configuration>

  <system.web>
    <compilation debug="true" targetFramework="4.0" />
    <customErrors mode ="Off">
    </customErrors>
  </system.web>
  <system.serviceModel>
    <services>
      <service name="aim_wcf_service.NIM_Latency" behaviorConfiguration ="aim_wcf_service.Service1Behavior">
        <endpoint address="https://services.oscautomation.com/NIM_Latency.svc" binding="wsHttpBinding" bindingConfiguration="TransportSecurity" contract="aim_wcf_service.IService1"/>
        <endpoint address="mex" binding="mexHttpsBinding" contract="IMetadataExchange"/>
      </service>
    </services>
    <bindings>
      <wsHttpBinding>
        <binding name ="TransportSecurity">
          <security mode="Transport">
            <transport clientCredentialType="None"/>
          </security>
        </binding>
      </wsHttpBinding>
    </bindings>
    <behaviors>
      <serviceBehaviors>
        <behavior name="aim_wcf_service.Service1Behavior">
          <!-- To avoid disclosing metadata information, set the value below to false and remove the metadata endpoint above before deployment -->
          <serviceMetadata httpsGetEnabled="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>
    <serviceHostingEnvironment multipleSiteBindingsEnabled="false" />
  </system.serviceModel>
  <system.webServer>
    <modules runAllManagedModulesForAllRequests="true"/>
  </system.webServer>

</configuration>


if anyone has any ideas on what could be causing this or ways that i could research this further please let me know. Also if it matters this service is hosted in iis6.
Posted

1 solution

I figured this one out! On Win XP 32 bit, for some reason the client never looks at the configuration given to it by the service reference, so I ended up hard coding everything into my wcf client code and everything started working as expected.
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900