– I have a wsHttpBding WCF service, please refer to the service configuration below
– I have implemented ServiceHostFactory to solve the incorrect pattern location and soap address The problem, modify them from the machine name to the correct server host name
-My test client (WCFStorm) I can generate proxies, view all methods and call them successfully.
-My development environment (customer Client –> HTTPS –> Service) works perfectly.
Question:
– prod environment (client –> HTTPS –> F5 –> HTTP –> service)
– I The service is an F5 load balancer that supports SSL uninstallation
-My test client (WCFStorm) I can generate a proxy and view all methods, but when I call any method, I get a 404 error that the remote server is not found
>My service configuration:
< service behaviorConfiguration = "Service1Behavior"
NAME = “MyService” >
< endpoint address = "mex" binding = "mexHttpsBinding" contract = "IMetadataExchange"/>
/Service>
< /Service>
<&wsHttpBinding GT;
< /Security>
< /Combination>
< /& wsHttpBinding GT;
< /Binding>
< serviceDebug includeExceptionDetailInFaults = "true"/>
< dataContractSerializer maxItemsInObjectGraph ="6553600"/>
< /behavior>
< /serviceBehaviors>
< /behavior>
>Please Note that all the architecture locations and soap addresses on wsdl are correct in prod, but I can’t call any methods at all.
Please help.
In service – we changed the binding To use basicHttpBinding and add a key that must be passed with each request.
On the client side-we change the http in the configuration to https, and change the security mode to Transport with clientCredentialType in the basicHttpBindings configuration =”None”.
Hope this helps.
Update: I found this article soon, I updated the configuration and it worked fine. So now we use wsHttpBinding Instead of basicHttpBinding.
http://blogs.msdn.com/b/morgan/archive/2010/04/15/setting-up-wcf-wit ha-load-balancer-using-ssl-in-the-middle.aspx
Current settings:
– I have a wsHttpBding WCF service, please see below Service configuration
-I have implemented ServiceHostFactory to solve the problem of incorrect mode location and soap address, and changed them from the machine name to the correct server host name.
-My test client (WCFStorm) I can Generate proxy, view all methods and call them successfully.
– My development environment (client-> HTTPS-> service) works perfectly.
Question:
– prod environment (Client-> HTTPS-> F5-> HTTP-> Service)
-My service is an F5 load balancer that supports SSL offloading
-My test client (WCFStorm) I can generate a proxy and view it All methods, but when I call any method, I get the remote server not found 404 error
>My service configuration:
< /Service>
< /Service>
<&wsHttpBinding GT;
< /Security>
< /Combination>
< /&wsHttpBinding GT;
< /Binding>
< serviceBehaviors>
< serviceDebug includeExceptionDetailInFaults ="true"/>
< dataContractSerializer maxItemsInObjectGraph ="6553600"/>
< /behavior>
< /serviceBehaviors>
< /behavior>
< p>>Please note that all the architecture locations and soap addresses on wsdl are correct in prod, but I can’t call any methods at all.
Please help.
< p>
We have a similar situation, this is how we make it work.
In the service – we changed the binding to use basicHttpBinding and added a must The key passed with each request.
On the client side-we change the http in the configuration to https, and change the security mode to Transport with clientCredentialType = “None” in the basicHttpBindings configuration.
Hope this can help.
Update: I found this article soon, I updated the configuration and it worked fine. So now we use wsHttpBinding instead of basicHttpBinding.
http ://blogs.msdn.com/b/morgan/archive/2010/04/15/setting-up-wcf-with-a-load-balancer-using-ssl- in-the-middle.aspx