405 Method Not Allowed Issued by WCF Service Running Under IIS7 with SSL

I'm having a major issue with configuring a WCF service in production. We are running on IIS7 and we have an SSL certificate installed. One important detail is that I have mapped my web service to a new "Web Site" running over port 5755, which accepts only https bindings. I dont know if this has anythig to do with the problem, but its the only abnormal configuration I can think of. I am able to browse to my service just fine using the URL. I can also download the WSDL just fine. What happens is when I try to execute a method on the service (which I believe issues a post), I get a 405 method not allowed error. I've tried many variations in the configuration, and checked everything on IIS, and I'm now at a total loss. IIS is configured to handle WCF services (first thing I checked). It is configured to allow all VERBS (GET, POST, DELETE, etc). So far nothing has been successful. I've included a sample of my web service configuration file. For security I removed the actual URL, but I thought it might be helpful in diagnosing the issue. I do not believe however this has anything to do with the configuration, and is probably more likely an obscure IIS issue.
<system.serviceModel>
    <bindings>
      <basicHttpBinding>
        <binding name="ServiceBinding">
          <security mode="TransportWithMessageCredential"></security>
        </binding>
      </basicHttpBinding>
    </bindings>
    <behaviors>
      <serviceBehaviors>
        <behavior name="SharedService_Behavior">
          <serviceDebug includeExceptionDetailInFaults="false" />
          <serviceMetadata httpsGetEnabled="true" httpsGetUrl="https://myurl:5755/SharedService.svc" />
        </behavior>
      </serviceBehaviors>
    </behaviors>
    <services>
      <service name="OFH.EPM.Business.Shared.Service.ServiceImplementation.SharedService" behaviorConfiguration="SharedService_Behavior">
	<endpoint address="https://myurl:5755/" binding="basicHttpBinding" bindingConfiguration="ServiceBinding"
          name="SharedServiceEndpoint" bindingNamespace="https://myurl:5755/"
          contract="OFH.EPM.Business.Shared.Service.ServiceContracts.ISharedService" />
      </service>
    </services>
  </system.serviceModel>

Open in new window

jmmobley1978Asked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Grant SpiteriConnect With a Mentor Senior consultantCommented:
I have setup exactly same scenario but we just encrypt the pipe not the message for performance below is the binding we use but also have to make sure that the consuming application needs to match certificate's

<binding name="ServiceBinding"  closeTimeout="1:00:00"
                 openTimeout="1:00:00"
                 receiveTimeout="1:00:00"
                 sendTimeout="1:00:00">
          <security mode="Transport">
            <transport clientCredentialType="Windows" />
          </security>
        </binding>
0
 
jmmobley1978Author Commented:
This was not the solution, but it seems no one in the community is willing or able to provide an answer for this issue so I'm closing it. Thanks for your help.
0
All Courses

From novice to tech pro — start learning today.