The past couple of weeks I'm working with Silverlight controls embedded in SharePoint 2007. For one of the controls I need to retrieve the data using the Search Query Web Service. This was working perfectly in the development environment. But when deploying the control to the production environment it didn't work.
The past couple of weeks I am working with Silverlight controls embedded in SharePoint 2007.
For one of the controls, I need to retrieve the data using the Search Query Web Service.
This was working perfectly in the development environment.
But when deploying the control to the production environment it did not work.
I was using the following code:
After some digging, I found that the control did actually work,
but only when the page was visited over an HTTP connection.
As visitors were accessing the page over an HTTPS connection,
I was pointed in the direction of the connection between the control and the web service.
As can be seen in the code the WCF client is used and I remembered that the binding security mode is different if you want to work with HTTPS.
So, I changed the BasicHttpSecurityMode from None to Transport.
After deploying the control again, it worked nicely over the HTTPS connection,
so I knew what the source of my problem is.
But naturally I want a generic solution so the configuration of the access mapping is not influencing the functioning of the control.