This is the case, the department has a Sliverlight project, and now for the security of the site is to use the HTTPS,HTTPS certificate configuration is done on another UNIX server, the user will pass through it to their ABC three Windows Server, The SL project is deployed on the IIS of the win server. The WCF service for SL projects uses BasicHttpBinding and does not use secure authentication configuration. After the initial configuration, the login page can be accessed, but the WCF service cannot be called. To solve this problem, an article on the HTTPS configuration of WCF was found online:
1, http://www.cnblogs.com/coolkiss/archive/2010/07/14/1777077.html and my situation is not quite the same, but also a kind of application scenario, keep.
2, Https://www.codeproject.com/Articles/36705/simple-steps-to-enable-HTTPS-on-WCF-WsHttp-bindi Many articles have mentioned this, The foreigner's description is very fine, the next source does not need points or something, very good. But I don't need to configure IIS, and things are not the same.
3, Http://timheuer.com/blog/archive/2008/10/14/calling-secure-services-with-silverlight-2-ssl-https.aspx This is the final solution to the problem. Because the Web page resources and services are brokered to the win server IIS, so the service does not need to have any change, need to change is the client. Only the security mode that requires binding is changed from none to transport.
<BasicHttpBinding> <bindingname= "Basichttpbinding_iservice1"maxBufferSize= "2147483647"MaxReceivedMessageSize= "2147483647"> <SecurityMode= "Transport" /> </binding> </BasicHttpBinding>
SILVERLIGHT+WCF Project HTTPS Configuration